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
Right now when a diagnostic refers to a method, it does so by only using its name. This gets confusing when traits and templates come into play, as it gets hard to distinguish which type the method belongs to. The solution would be to make methods aware of their "fully-qualified" names that include the whole path from the root namespace to the method name. An example of such name could be Foo::bar for a method bar of type Foo.
Right now when a diagnostic refers to a method, it does so by only using its name. This gets confusing when traits and templates come into play, as it gets hard to distinguish which type the method belongs to. The solution would be to make methods aware of their "fully-qualified" names that include the whole path from the root namespace to the method name. An example of such name could be
Foo::bar
for a methodbar
of typeFoo
.Need to consider #4 when designing the solution.
The text was updated successfully, but these errors were encountered: