Wouter van Oortmerssen

To elaborate on my original post, when I mentioned that I'd rather have a co-routine feature that would translate to existing functionality, I mean something like this: ``` coroutine co(n:int):...

I've been thinking about other co-routine-like features that are less "heavy" than an actual co-routine. Essentially, with a co-routine you have a function call that can be cut down the...

Aaand.. it is done.. co-routines are gone. The last version of the language that does contain co-routines is marked with the label `last_coroutine` in git, and the diff showing exactly...

@JobLeonard Thanks for the explanation! I am actually somewhat familiar with both Esterel and Céu already, as I've done a fair bit of design around dataflow languages, and find these...

@JobLeonard was not aware it had "unlimited" pools, indeed! While I love the strict lexical / nested resource / lifetime management (I am actually designing a language currently that does...

Relevant: mistakes made in C++ co-routines: https://probablydance.com/2021/10/31/c-coroutines-do-not-spark-joy/

Hah, @Verdagon who wrote those is a friend, and I am familiar with his work.. but Lobster already optimizes reference counting by quite a bit more than half in a...

Certainly, optimizing that remaining 5% of runtime refcounts is not the current "low hanging fruit" in making Lobster faster, it would be quite a bit of work to support for...

> BTW, Wouter, I gave you some shout-outs on https://news.ycombinator.com/item?id=31139610 =) Ooh thanks :)

Yup, this is to some extend a known issue, but should probably at least be better documented. Mentioned here in the TODO.txt: https://github.com/aardappel/lobster/blob/da09a2c36dfe4ce45699e53ce5f032cbefaf18ea/dev/TODO.txt#L208-L228 I am thinking that at this stage,...