You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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. 👍
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.The text was updated successfully, but these errors were encountered: