Skip to content

Simpler design alternatives #5

@popcron

Description

@popcron

the design right now looks like this:

  • simulators can have systems added to
  • simulators are aware of program entities
  • when a simulator updates forward, they update systems and then programs

and its quite a lot of steps, feels like the underlying code is jumping through more hoops than it needs to. i dont think it should be that way, and the reason why the design is as such is so that one simulator instance can be created, while multiple programs can be made to run in sequence or parallel:

using World world = new();
using Simulator simulator = new(world);
using Program<A> a = new(world);
using Program<B> b = new(world);
while (!b.IsFinished && !a.IsFinished)
{
    simulator.Update();
}

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions