Stack traces

[scizzorz]

They don't exist - what's the best way to implement them?

A rudimentary version I had much earlier in development simply maintained a static, fixed-size buffer of "coordinates", which consisted of a line, column, and qualified module name. Each function call would inject its own coordinates into the buffer when it began execution and then pop them off when returning. Didn't seem very futureproof to me, though.

[scizzorz]

These are mostly working in master but there's a few places that need to be traced - notably, indexing (calls to rain_get, rain_put, etc).