C# 7.0 tuples #1134
Merged
C# 7.0 tuples #1134
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
* Use tuple literals instead of calling 'new ValueTuple<..>' constructor * Where available, use element names for field access * Make CallBuilder aware of tuple-name/dynamic type erasure, to avoid introducing casts when the types differ only in the tuple element names. * Make CallBuilder provide a ResolveResult with the correct C# return type for the resulting expression. Previously we were using the type-erased return type from the IL. * Fix a bug that caused us to introduce returning casts when accessing an indexer.
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.
Just as
objectanddynamicare two different C# types that map to the same IL type; tuple types are a bunch of new C# types that map to the normalValueTuple<>struct types.Note: deconstruction is a separate topic.