mfunk

~~Since we already can create new arrays with some capacity (but not length), what about something like `ensure_capacity `, which would allow implementers to get rid of unnecessary allocations if...

>I'll point out the curly braces :O > getNestedObject() => I'd rename to just getExcVal() Done The following approach is currently implemented: * `throw` simply throws the argument value and...

> Currently, every call site has an src_pos attribute which we can report in the stack trace. It's a bit hard to use, since we can't look at the call...

> This is why I added a retEntry map in vm/interp.cpp. So that we can associate meta-information with return addresses (each one has an associated RetEntry). We should probably store...

Great. Should a stacktrace object/array be attached to the exception value, if it is catched? This would allow manual printing and/or introspection by the user or the runtime. A language...

Once again, I have to apologise for my absence. I should have at least shared my progress on this issue before staying silent for two months. https://github.com/krypt-n/zetavm/commit/82c0995e97ca5dad5dcbbbae7d39fc0fc3f5ba2b test.pls: ``` #language...

Nothing in particular. Is `hostCall` the only place that needs to convert from RunError to zeta exception? And do we need an explicit conversion or can we just pass the...

``` ERROR: math is currently not available in rt_throw at unknown location in top-level at unknown location in import (host function) at unknown location in top-level at test.pls@3:9 ``` *...

> In the case of zeta exception -> RunError, I'm not sure. We technically could wrap zeta exceptions I suppose, but I think at the moment I'm unwrapping them so...

`top-level` is just the name that plush codegen gives the top-level function. The exception handling doesn't differentiate between it and normal functions