-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
C#: Use C'X
fully-qualified-name format instead of C<,...,>
#14589
Conversation
C
X FQN format instead of
C<,...,>`C
X` FQN format instead of
C<,...,>`
C
X` FQN format instead of
C<,...,>` C
X ` FQN format instead of
C<,...,>`
C
X ` FQN format instead of
C<,...,>`C'X
FQN format instead of C<,...,>
C'X
FQN format instead of C<,...,>
C'X
fully-qualified-name format instead of C<,...,>
8694747
to
9fd38b6
Compare
f75d903
to
ccaa530
Compare
|
ccaa530
to
7bc094d
Compare
7bc094d
to
bcf4d7a
Compare
bcf4d7a
to
57ec094
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. Mostly based on that CI is green and there's no MaD change in the PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work @hvitved !
This PR changes our rendering of fully qualified names for unbound generics from the non-standard
C<,...,>
format, to the standardC`X
format, whereX
is the number of type parameters. This is, of course, a breaking change, so instead of directly changing{has,get}QualifiedName
to use the new format, I have instead deprecated{has,get}QualifiedName
, and introduced new{has,get}FullyQualifiedName
predicates that use the new format.The existing
getName
predicate has been adjusted, so it also uses the new format instead of the old format, here it was not natural to deprecate the predicate and come up with a new name.