Twitter: @toddjonker
Our current implementation predates the scope-set paper, so it follows the historical algorithm. Which means the code is SUPER hard to understand and probably buggy. Replacing it isn't a priority right now, but I'm itching to replace it.
Our current implementation predates the scope-set paper, so it follows the historical algorithm. Which means the code is SUPER hard to understand and probably buggy. Replacing it isn't a priority right now, but I'm itching to replace it.
I’d particularly love to see how Racket implements binding resolution and scope sets.
I’d particularly love to see how Racket implements binding resolution and scope sets.