tracing for otherwise combinator

orc-lang / orc

Orc programming language implementation

https://orc.csres.utexas.edu/

BSD 3-Clause "New" or "Revised" License

42 stars 3 forks source link

tracing for otherwise combinator #2

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

The tracer does not trace the otherwise combinator. It should probably
mirror the pruning combinator, with events analogous to "pull", "store",
"block", and "unblock".

Also, when a token is killed on reading a dead future, this is not
reflected in the trace; it should appear as a block/die even if the future
is already available. (Similarly, we can get rid of readFuture or whatever
it is called and replace it with block/unblock).

Original issue reported on code.google.com by adrianqu...@gmail.com on 11 Apr 2009 at 1:15

GoogleCodeExporter commented 9 years ago

Original comment by adrianqu...@gmail.com on 15 Apr 2009 at 3:40

Added labels: Milestone-Next

GoogleCodeExporter commented 9 years ago

Original comment by dkitc...@gmail.com on 3 Sep 2009 at 8:04

Added labels: Priority-Low
Removed labels: Priority-High

GoogleCodeExporter commented 9 years ago

Original comment by dkitc...@gmail.com on 3 Sep 2009 at 8:05

Removed labels: Milestone-Next

GoogleCodeExporter commented 9 years ago

Original comment by dkitc...@gmail.com on 22 Feb 2010 at 8:09

GoogleCodeExporter commented 9 years ago

Handing this issue to Sidney, since he is working on causality tracking.

Original comment by dkitc...@gmail.com on 9 Mar 2010 at 8:19

GoogleCodeExporter commented 9 years ago

OrcJava's tracing facility will be replaced by a future OrcScala tracing 
facility

Original comment by jthywissen on 17 Jan 2011 at 6:11

Changed state: WontFix