Better error reporting, but it breaks rock compilation
Well, that almost produces correct code.. the closurization of FTypes doesn't work though. Hmph
Time stuff
Handles closures correctly again. Closes #700
Fixes upon fixes
Woopsie, we already had a codename for that..
Document middle/Node, add 'refresh' method. I have something in mind..
Implement isResolved for middle/Cast
Don't segfault if case expr is null in Case toString()
Refresh node after their hierarchy has been modified in autoReturn
Mark funcTypeDone as true if we're not in a suspicious node type. Conflicts with autoReturn for now
Implement refresh for VariableAccess, solves our problems it seems?
Err when an additional import would be required. Closes #704
Debug--
Merge pull request #706 from shamanas/98x

Returning something from a void function now throws a rock error. Closes #449
Merge pull request #707 from shamanas/98x

Disallow floating point numbers with no digits
Merge pull request #708 from shamanas/98x

Added raw string support from conspiracy
Merge pull request #709 from shamanas/98x

Fixed bootstrapping, ironically broken due to the new return check that uncovered an error in the existing rock codebase
Merge pull request #710 from shamanas/98x

Added a simple string interpolation test, removed some unused code
Merge with fcall