On Thu, 08 Sep 2016 12:55:10 -0700, sml...@gmail.com wrote:
> If you `die` inside a `map/for` that is being `hyper/race`d...
>
> for (1..1).hyper { die }; sleep 1; say "Alive";
>
> ...it prints the exception's backtrace, but then resumes the program
> as if nothing had happened:
>
> Died
> in block at -e line 1
>
> Alive
Fixed in new hyper/race implementation; tests in S07-hyperrace/hyper.t and
S07-hyperrace/race.t. The new error reporting shows the backtrace of both the
thing that went wrong in a worker thread, and the place that triggered the
iteration.
