Scheduler "resume" is ill-defined

[GoogleCodeExporter]

Resuming an engine is a very ill-defined operation especially if the graph 
changes.
For instance, if engine terminates due to a termination-condition, and 
#vertices in the graph changes, it is necessary to
  1:  update the scheduler datastructures to reflect the new size of the graph
  2:  remove invalid tasks (tasks which point to non-existant vertices)

Some of these could be difficult to implement for many schedulers.

I suggest that scheduler-resuming support be totally removed.

Engine should:
 - Construct scheduler on get_scheduler() or engine->start() whichever comes first.
 - Destroy scheduler on engine termination.

Original issue reported on code.google.com by yucheng...@gmail.com on 12 Oct 2010 at 5:49

[GoogleCodeExporter]

In general, scheduler semantics are not too well defined. To document and make 
clear what each function means.

Original comment by yucheng...@gmail.com on 3 Nov 2010 at 8:50

• Added labels: Milestone-Release1.0, Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Also add functions "add_task_to_neighbors" to callback.

Original comment by yucheng...@gmail.com on 3 Nov 2010 at 8:51

[GoogleCodeExporter]

Original comment by yucheng...@gmail.com on 6 Feb 2011 at 6:46

• Changed state: Fixed