[racket] A puzzle

If you need to examine a large set of execution sequences, a debugger
wouldn't really help.  I think you want a custom evaluator written to
explore exhaustively the space of possible context switches (e.g., via
backtracking).

Greg

On Wed, Jan 19, 2011 at 4:26 PM, Mark Engelberg
<mark.engelberg at gmail.com> wrote:
> Hmm, I don't think the greedy approach will work.
> The first line of the second thread,  (set! a (list c)), will execute
> without error immediately, but it really needs to happen between the
> evaluation of a and (first a) in the first line of the first thread.
>
> Probably needs to be done by hand.
> _________________________________________________
>  For list-related administrative tasks:
>  http://lists.racket-lang.org/listinfo/users
>