Incorrect warning in vscode extension

[Harsche]

This is the warning:

But it is possible for static variables:

It would also be nice to get autocomplete suggestions for static variables when accessing constructs this way.

[adam-coster]

Since static variables only exist after a function/constructor has been called once, they live in a weird state where Stitch can't easily tell for sure if they exist when they are accessed via dotting into the function/constructor itself. So in our own code we just sorta never use this pattern, which is why I hadn't sorted it out how to track it in Stitch.

That said, I totally agree that this is a useful pattern that Stitch should support. It'll take some doing to get there, since the parser code is pretty complicated and at the moment functions are assumed to just be callable things for simplicity. I'm not sure when I'll get to it, but I'll keep this high on my feature list!