Support type modifiers in type id name resolution. #367
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Ok I guess this allows some tricks with |
cowtowncoder
added a commit
that referenced
this pull request
Dec 14, 2013
Support type modifiers in type id name resolution.
cowtowncoder
added a commit
that referenced
this pull request
Dec 14, 2013
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit adds the ability to use type modifiers in conjunction with TypeNameIdResolver. Previously, the type name was resolved from the actual type. This change makes use of the type modifier to resolve against the modified type.
The included test patches just the one resolver, which fixed my use case. It may be the case that the other resolution strategies should also account for the presence of type modifiers. Any guidance there would be appreciated. Thanks!