Saem Ghani

> two points: > > * AST based overloading is not tied to or specialized for macros. It is tied to overload resolution. Therefore it should not be listed in...

> @saem > > ```nim > proc foo(arg: int{nkIdent}) = > echo "it is an ident" > > proc foo(arg: int{nkSym}) = > echo "it is a sym" > >...

> What do you think about also including artifact related assertions? E.g. assertions for binary size, generated code, etc. Very much so, they're already supported in the current incarnation and...

Added compilation concepts, this is going to be a bit subtle, because we'll likely want to layer then out too. So for example, resolution of paths vs import names is...

If they're not tracked elsewhere then methods under inheritance.

This video from racket conf offers a better solution for alternatives and handling multiple groups to be associated with a previous line: https://youtu.be/UUWYTW3Xck8 Preview: ``` foo(stuff): | One statement Still...

Again this organization is great, it's pointing out the layers and dependencies really nicely. In that vein, I believe for loops should be rearranged a bit: - arrangement 1: be...

That looks good, I think some straightforward unit tests might capture much of this. What you're suggesting sounds reasonable, however.

How tricky would it be to make work in jsgen?

Just had a look through the tests, looks like hot code reload tests are failing. I'm wondering if we're injecting clears when we shouldn't during reload. Either that or maybe...