Iterable execution

Registered by Joshua Harlow on 2014-04-10

Instead of forcing all execution to be blocking (which requires spawning a greenthread, or real thread to not block the main program) allow for the execution to be somewhat iterable so that it can yield back at key points (letting other programs run in the meantime).

This will be a first step toward a more lazy like engine that can not-block the full process (or require spawning threads/greenthreads) while execution occurs.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Medium
Drafter:
Joshua Harlow
Direction:
Needs approval
Assignee:
Joshua Harlow
Definition:
New
Series goal:
Accepted for 0.3
Implementation:
Implemented
Milestone target:
None
Started by
Joshua Harlow on 2014-05-04
Completed by
Joshua Harlow on 2014-05-08

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.