Yes. The problem is that Julia (and I) don't know who to run after this point: there were no tasks scheduled to run and it didn't seem reasonable to wake a random task to throw the error again. If you use enq_work instead of yieldto, it should behave better.

e.g. we don't want to have `println` in the following example throwing `error("oops")`, since that point in the code has no relation to the task that it both created (`.parent`) and spawned (`.last`):
```julia
@async error("oops")
result = some_long_computation()
println(result) # calls wait(), which finally runs `async`
```

I'm thinking of following microsoft's lead here and creating a `SetUnhandledExceptionHandler` function so the user gets to decide :)