-
Notifications
You must be signed in to change notification settings - Fork 6k
Continued response to Tuple topic feedback #2292
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
Conversation
Much of these had been addressed by @svick. Adding the remaining open items.
@terrajobst Can you review my edits on types on which language features depend and .NET standard? I want to make sure it's accurate. /cc @richlander |
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.
Aside from one comment, LGTM.
@@ -25,10 +25,20 @@ In this topic, you'll learn the language rules governing Tuples in C# 7, | |||
different ways to use them, and initial guidance on working with Tuples. | |||
|
|||
> [!NOTE] | |||
> The new tuples features require the `System.ValueTuple` type. For Visual Studio 2017, | |||
> you must add the NuGet package [System.ValueTuple](https://www.nuget.org/packages/System.ValueTuple/), available on the NuGet Gallery. | |||
> Without this package you may get a compilation error similar to `error CS8179: Predefined type 'System.ValueTuple``2' is not defined or imported` |
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.
We should add CS8137 and CS8179 to the sorry-we-don-t-have-specifics... file in the C# compiler error messages directory. I'll open a quick PR to do it and add a few others.
docs/csharp/tuples.md
Outdated
> on platforms that do not include the types. | ||
> | ||
> This is similar to other language features that rely on types | ||
> delivered in the framework. Example include `async` and `await` |
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.
Example --> Examples
> features rely on new types, those types will be available as NuGet packages when | ||
> the language features ship. As these new types get added to the .NET Standard | ||
> API and delivered as part of the framework, the NuGet package requirement will | ||
> be removed. |
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.
Sounds good to me :-)
Fixes #1889
Much of these had been addressed by @svick in PR #1842. Adding the remaining open
items.