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

Address Interpolated Strings test plan #55701

Merged
merged 6 commits into from
Aug 21, 2021
Merged

Address Interpolated Strings test plan #55701

merged 6 commits into from
Aug 21, 2021

Conversation

333fred
Copy link
Member

@333fred 333fred commented Aug 18, 2021

Addresses remaining compiler items on the interpolated strings test plan: #51499. I would highly recommend commit-by-commit review for these. The first few commits add tests and fix small bugs found with the tests. The last commit bundles the tests that were simply added with no other changes necessary.

@333fred 333fred requested a review from a team as a code owner August 18, 2021 18:39
@333fred
Copy link
Member Author

333fred commented Aug 18, 2021

@chsienki @jcouv for review

@jcouv
Copy link
Member

jcouv commented Aug 18, 2021

Looks like there's a couple of test failures


In reply to: 901449708

@333fred
Copy link
Member Author

333fred commented Aug 19, 2021

@jcouv should be fixed, please take a look.

@@ -825,7 +825,16 @@ private ImmutableArray<BoundExpression> BindInterpolatedStringParts(BoundUnconve
var interpolatedStringConversion = memberAnalysisResult.ConversionForArg(interpolatedStringArgNum);
Debug.Assert(interpolatedStringConversion.IsInterpolatedStringHandler);
var interpolatedStringParameter = GetCorrespondingParameter(ref memberAnalysisResult, parameters, interpolatedStringArgNum);
Debug.Assert(interpolatedStringParameter.Type is NamedTypeSymbol { IsInterpolatedStringHandlerType: true });
Debug.Assert(interpolatedStringParameter is { Type: NamedTypeSymbol { IsInterpolatedStringHandlerType: true } }
#pragma warning disable format
Copy link
Member

Choose a reason for hiding this comment

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

nit: Do we need a tracking issue for formatting problem?

Copy link
Member Author

Choose a reason for hiding this comment

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

@sharwell, do you know if there's a tracking issue for the formatter pulling this or all the way to the right, rather than leaving it aligned as it?

Copy link
Member

@jcouv jcouv left a comment

Choose a reason for hiding this comment

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

Done with review pass (iteration 7)

@333fred
Copy link
Member Author

333fred commented Aug 20, 2021

@jcouv any more feedback? @chsienki, please take a look.

Copy link
Member

@jcouv jcouv left a comment

Choose a reason for hiding this comment

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

LGTM Thanks (iteration 9). Still would recommend small spec change. Region analysis will be fixed later per offline discussion.

@333fred
Copy link
Member Author

333fred commented Aug 20, 2021

LGTM Thanks (iteration 9). Still would recommend small spec change. Region analysis will be fixed later per offline discussion.

Followed up on the spec offline. There is already a note about erroring in the case of bad info.

@333fred 333fred enabled auto-merge (rebase) August 20, 2021 18:06
@333fred 333fred merged commit 50605e9 into dotnet:main Aug 21, 2021
@ghost ghost added this to the Next milestone Aug 21, 2021
@333fred 333fred deleted the test-plan branch August 21, 2021 04:50
@dibarbet dibarbet modified the milestones: Next, 17.0.P4 Aug 31, 2021
@333fred 333fred added the Feature - Interpolated String Improvements Interpolated string improvements label Sep 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants