Simon Ask Ulsnes

This is actually a bug, due mostly to laziness on my part. It's on my roadmap to split the base classes into a Class object and an instance prototype, the...

There is already preliminary support for `copy` on the C++ side, actually. I'm not sure it's hooked up to the Snow runtime, but all classes deriving from `snow::IObject` should implement...

I think prelude.sn should be a list of require()s, including the base standard library (class, etc.). Having it in a single file makes the C++ side less dependent on the...

`__FILE__` and `__LINE__` are what people know, so why not. Also, they can be implemented directly in the parser with very little effort.

I concur.

As long as it gets a sensible string conversion, I'm all for it.

Not a bad idea at all. The feature is specific to interactive mode, right?

I do not believe I possess the dexterity required to do that. But yeah, good point. It can be done already, using the amazing(ly undocumented) dlopen/ExternalLibrary features. However, for debugging...

There's no technical reason why we shouldn't be able to simply save the AST subtree for a function during compilation, so it could be accessed later. It could also be...

Serializing closures this way is not necessarily a good idea. Closures, by nature, are context-dependent. Namely, they depend on the context in which they are defined, and can reference parent...