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
Being an "id" looks to me like it should be able to uniquely identify a method (or generally any member, being namespace, method, type, property, event).
It is and this example is indeed not unique.
At the same time, the format is established and is used for example for tooling scenarios to power C#<>F# navigation.
Given the likelihood of this happening in a real codebase, I think it does not justify changing the format for generated ids, no matter how hypothetically possible.
Language tooling relying on xmldoc ids should however be robust to not crash when a duplicate is encountered. A worsened experienced would be understood in this scenario IMO.
Being an "id" looks to me like it should be able to uniquely identify a method (or generally any member, being namespace, method, type, property, event).
In a niche case like the following:
Both methods will have the same id:
The text was updated successfully, but these errors were encountered: