Asynchronous env.exit() is undesirable!?

[plajjan]

Hmm, so I was a little perplexed over how my program apparently did things after I called env.exit(0), which I suppose must be because it will run async since there is no assignment happening. Changing to

foo = env.exit(0)

fixes it by exiting immediately as I expected.

Is this good? We've talked about async before, what to do implicitly and what to do explicitly (i.e. require keywords). Not sure if there is something new to be said. Maybe just complete our documentation and move on ;)

[plajjan]

@nordlander and I discussed this. It is likely that the wanted behavior here is to run env.exit() synchronously but making exceptions in the compiler is bad. One idea would be for env to not act as an actor but an object or methods on the own actor? Special but still sort of fits in the overall model.

I think this is mostly about the learning curve and I still think too much in Python and get surprised over the sync/async behaviour.

The idiomatic way to fix this is doing await async env.exit(0). I'll close this for now and maybe we'll revisit in the future... or maybe not ;)