Hostile Fork

I would say that it's a bad design to have two method signatures that differ only in optionality for a type. Interface-wise that sounds like it should be ambiguous...?

_(Note: my code needed to account for the non-optional initializations as well, to be a good demonstration. Fixed.)_ With the suggested change: your Tool case would favor the `int` constructor...

Cool, thanks. Pretty much any of those work for me, as long as the basic behavior is available!

Not the right way to go because... (?) I don't see why doing the same thing that happens when dereferencing a `nullopt` in other cases would be taboo. That is...

> I expect optional to bare resemblance to optional. That old StackOverflow question I cited (that you weighed in on) is where I felt the understanding had been hammered out...

_(Note: example previously wouldn't compile, pasted a bad version somehow. Edited.)_ To add another point on this issue, it's possible to re-assign an optional reference such as with ``` obr...

Will be good to see abstract types work. I've opened a new issue for the other concern--apologies in advance.

Great. I know that it may not be obvious what to do with the error once you get it, but it can at least point in the right direction. Here's...

> [2021-12-10 16:41:13.864] [error] When linking module: "env" , function name: "invoke_iii" These invoke instructions are put in automatically by Emscripten when you use setjmp()/longjmp() ([which you are using in...

If this is to be an "issue" proper, perhaps the issue can be about pawn promotion syntax. Could/should there be a standard, or is it beyond the scope of the...