Simon Ask Ulsnes

That is indeed a bug, probably in the codegen. Weird thing is that it's always the same number – maybe it's memory poison. Prioritizing...

This is probably related to #26; I will look into it. Also, please provide revision and architecture. :)

The reason this works in Interactive Snow ``` { return it }(60) //=> 60 ``` is an error in the parser. This would give the same result: ``` { return...

Good point. What do you suggest?

Should throw an exception. Marking as bug.

I concur. There is a minimum of insultingly inadequate info available at http://snow.meta.io/ . We currently lack a doxygen-like solution that can autogenerate unified documentation from both Snow and C++...

Good idea!

Correct. I'm imagining an Array (as now), with a map of symbols=>indexes. This way, the map can be stored in the function definition, as to avoid recreation every time a...

Hrm, another thing: The map can't necessarily be stored in the Function object, if we decide to allow custom named arguments, like options hashes in Ruby, which I strongly believe...

What do you suggest is the behavior in this case: Time.new(12, 0, 0) + Time.new(13, 0, 0) = ? ... and how would that deal with leap seconds? I would...