Adrian Sampson

Sorry; I don't have experience trying to run things on Windows. Maybe building a small test script (and inserting print-debugging) would help diagnose the problem?

No, integrating with a native green threads implementation would likely be quite difficult. Maybe Python's standard asyncio has considered that?

Ah yes, that does make sense—join should exit immediately for finished coroutines. The weak-reference idea seems like the right one, unless we want to simplify the story and just say...

Yes, your idea is obviously the less error-prone one—thanks for taking a look! I'll be happy to merge.

This is an interesting case—I haven't really built support for (nor thought of a good idea for _how_ to support) using Bluelet within generators (coroutines) that you actually intend to...

Indeed—using a flat vector of values could really help. But I also agree with your initial premise: at the moment, we don't have many benchmarks that really do much intense...

We actually could now add source positions, since #161.

Yeah! Maybe just supporting plain old "classic" `for` loops would be a good start. You know, the kind with `for (var i = 0; i < lst.length; ++i)`. That seems...

Aha, that's interesting! You're quite right, of course, that the latter example, should not prune the `phi` for `a`. Anyway, dealing with undefined variables is extremely tricky here! I'd be...

I think you're on the right track, although I don't know 100% that this will fix the problem. (Maybe it will?) In short, just removing the copies from `__undefined` themselves...