> I'm not sure you want to see that, heh. I think I'll stick with the > "hover over a symbol to see it's compile-time representation" solution... Cool, didn't know scope was just syntactic sugar for such a construct. Well the question is what the output looks like for a test scenario that is more practical, such as mixins and stuff.