StackOverflowException thrown resolving not-so-ambiguous stuff

[retailcoder]

Identifier resolution code gets confused when it comes across Collection.Count and Matches.Count when there's a List.Count type/method in the project. This results in a fatal StackOverflowException being thrown.

[retailcoder]

Adding [vba-grammar] label, as I've seen an in-statement implicit member call come up as something else, and this is most probably what's branching the identifier resolution code into an infinite loop that ends up overflowing the stack.

[retailcoder]

I'm closing in on this one - turns out it's not happening with code that's trivial, or even advanced. I've only had the StackOveflowException on a project that implemented a full-fledged Model-View-Presenter with IRepository pattern - yes, I'm mad enough to have done that in VBA - thing is, even that crazy project parses fine... the SO exception is only thrown when the View gets involved. I have yet to find out why and how, but all modules, intefaces and implementations in this project parse fine, except the form, which implements an IView interface.

I'm going to keep investigating this issue, and very hopefully fix it. But I no longer consider it a critical must-fix-for-next-release issue, rather more of an edge case.

[retailcoder]

Rewritten resolver no longer blows up and completely processes that crazy project without any issues.