Saem Ghani

For those discovering this much later, the reason why this hasn't been accepted or moved forward is because it runs counter to how Nim tooling works. Note, I don't understand...

@g5becks do you have an open source Nim project where this it's easily replicated?

@saem, you jerk, look at this issue! 😄

The context within which the failure occurred likely knows best how to deal with resolving the issue, not some generic callback. Even if it can't be put on the persist...

Do we already have a test for that particular error path? Aside for later: need to think about how to make it easier to see the test vs error coverage.

I'll try and look on this weekend, my dance card is pretty full, too. Unless Hax beats me to it.

My currently terrible idea as to how to fix this would be to go into `sempass2.track` and for the `nkError` branch in the case statement do the reset of `TContext.recursiveDep`...

We know if there is a recursion problem in `myImportModule` but for reasons that I don't understand we don't act on it... that seems goofy. Am I missing something? In...

resurrected, this was far less painful, it's getting very close to allow for some discussion, just a few clean-up items but that can be somewhat concurrent. Immediate Items: - [...

I think a bunch of the procedure dispatch related to typed and untyped parameters needs to move here. 😅 We'll have topics revisited like that because a layer like macros...