Vasiliy Tereshkov

@Xceptionull It would. But what to do with the other examples? I don't want to impose so many artificial restrictions just to work around the memory management defect. Thankfully, this...

In Umka, no code can be executed outside functions, except for the initial jump to the `main` entry point. Therefore, you can use only constant expressions to initialize global variables....

@roastpiece This is very interesting as an experiment. However, I don't consider it to be part of the Umka interpreter, for the following reasons: * **Portability:** Umka should build with...

@roastpiece FYI, there is a related project being discussed on Discord: https://discord.com/channels/846663478873030666/1441947520468127916

@ske2004 These new external functions are not compatible with the conventional `fn ()` type.

@Readf0x You can get the Umka instance with `umkaGetInstance()`. Then you can store in it and retrieve from it any user data with `umkaSetMetadata()`/`umkaGetMetadata()`. This is a per-instance, rather than...

@Readf0x Can you provide a code example? Without it, I can hardly see what you are trying to get or why the per-instance data storage is not enough.

@Readf0x So your idea is to register _the same_ C function `externFuncShim()` under all possible Umka names. At this point, you, fairly enough, lose the information about what Umka function...

Go says "non-name b[0] on left side of :=".

@ske2004 Ah, you're right! It doesn't accept anything except an unqualified type name, because otherwise it would be hard to distinguish a type from an expression (an infinite lookup needed?)...