Wouter van Oortmerssen

Actually that one option mentioned in the TODO might be worth it: annotate the body call that it can't be returned out of. That would compile time error on any...

@maddanio how would you define a destructor for the above `def translate` example (in my TODO ref) ?

I have non-local returns, which have some of the same complexities as exceptions, see the top posts. Defer would not be super expensive, but it is also not super useful...

Yes, at program exit. What that means is that if you want to be using doubly linked lists, you must manually set to `nil` at least one of the links...

Let's just say that for all that I've used it for (games and compilers) it has not been an issue.. of ~100 or small to medium size programs I have...

Yes, would be good to know where it crashes. One thing is that if you try to run some Lobster code directly (not with `--cpp`), it will JIT the code...

I currently don't have an M1 machine to try this on.. ideally it would JIT straight to ARM, which it does have an implementation for.

There are no plans to change it from `_` to `.`, no. Other than personal preference, any reason?

That is not very practical for me. Lobster is a cross-platform code base (6 platforms: win/mac/linux/ios/android/wasm), and it is super important that dependencies are well tested against the current code,...

There currently aren't any.. Lobster is very much a "batteries included" kind of system, all the currently included libraries (mostly gamedev oriented) you can find here: http://aardappel.github.io/lobster/builtin_functions_reference.html A third party...