Properly handle static constructors
Opened this issue · 1 comments
As mentioned by @AmadeusW in #63, we need to handle static constructors properly. In C#, the fully qualified name of a static constructor is not enough to differentiate it from a parameterless constructor.
In another project, we solved this issue by adding an "isStatic" property to constructors. However, I'm not convinced that this is the best solution for Source Browser. It couples our model to the C# programming language.
Perhaps instead we can alter the fully qualified names of static constructors instead.
Namespace.Class.Constructor::static or something along those lines.
Altering the fully qualified name appears to be a good idea. After all, we're using just fully qualified name to do the mapping, and we don't use it for anything else. 👍