Skip to content

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

Merged
merged 2 commits into from
Jun 1, 2017
Merged

Continued response to Tuple topic feedback #2292

merged 2 commits into from
Jun 1, 2017

Conversation

BillWagner
Copy link
Member

@BillWagner BillWagner commented May 31, 2017

Fixes #1889

Much of these had been addressed by @svick in PR #1842. Adding the remaining open
items.

Much of these had been addressed by @svick. Adding the remaining open
items.
@BillWagner
Copy link
Member Author

@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

Copy link
Contributor

@rpetrusha rpetrusha left a 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`
Copy link
Contributor

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.

> 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`
Copy link
Contributor

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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good to me :-)

@BillWagner BillWagner merged commit d1b83ad into dotnet:master Jun 1, 2017
@BillWagner BillWagner deleted the clarify-tuples-1889 branch June 1, 2017 14:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants