Skip to content
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

Move to the real System.ValueTuple ref #74936

Merged
merged 7 commits into from
Sep 2, 2024
Merged

Move to the real System.ValueTuple ref #74936

merged 7 commits into from
Sep 2, 2024

Conversation

jaredpar
Copy link
Member

No description provided.

@jaredpar jaredpar requested review from a team as code owners August 28, 2024 21:24
@dotnet-issue-labeler dotnet-issue-labeler bot added Area-Compilers untriaged Issues and PRs which have not yet been triaged by a lead labels Aug 28, 2024
@jaredpar
Copy link
Member Author

@dotnet/roslyn-compiler PTAL


/*
* ⚠ Dev note ⚠: TestBase properties end here.
*/
Copy link
Member Author

Choose a reason for hiding this comment

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

This comment was moved up because the properties below no longer depend on TestBase

@333fred 333fred self-requested a review August 30, 2024 16:45
SymbolDisplayPartKind.Punctuation,
SymbolDisplayPartKind.Keyword,
SymbolDisplayPartKind.Space,
SymbolDisplayPartKind.StructName,
SymbolDisplayPartKind.Punctuation},
references:={MetadataReference.CreateFromImage(TestResources.NetFX.ValueTuple.tuplelib)})
references:={Net461.ExtraReferences.SystemValueTuple})
Copy link
Member

Choose a reason for hiding this comment

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

Net461.ExtraReferences.SystemValueTuple

Should we just use the legacy reference here, to avoid changing the expected result?

Copy link
Member Author

Choose a reason for hiding this comment

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

I thought about that but symbol display is a user visible artifact. Decided that it was better to have our tests track down Tuple displays in the 99.999% case vs. the .001% case that I'm not sure you can reaally achieve.

@jaredpar jaredpar enabled auto-merge (squash) August 30, 2024 23:15
@jaredpar jaredpar merged commit b19ecd7 into dotnet:main Sep 2, 2024
28 checks passed
@dotnet-policy-service dotnet-policy-service bot added this to the Next milestone Sep 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Compilers untriaged Issues and PRs which have not yet been triaged by a lead VSCode
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants