Improve generic type parsing and referencing#178
Merged
davideicardi merged 4 commits intodynamicexpresso:masterfrom Oct 30, 2021
Merged
Improve generic type parsing and referencing#178davideicardi merged 4 commits intodynamicexpresso:masterfrom
davideicardi merged 4 commits intodynamicexpresso:masterfrom
Conversation
… with different Arity. Properly parse constructor invocation of a generic type.
davideicardi
approved these changes
Oct 29, 2021
Member
davideicardi
left a comment
There was a problem hiding this comment.
Great! Just one question on the resx ...
This file contains hidden or 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
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.
The arity of the generic type is now considered when trying to get the reference type (e.g.
Tuple<,,>is now looked up asTuple`3during parsing).That means it's possible to write:
The old way is still working, but in that case you need to add the arity yourself:
I took this opportunity to also centralize the way types are parsed, so that it's consistent everywhere.
Fixes #174