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

VB: Do not use overload resolution while lowering interpolated strings #75449

Merged
merged 2 commits into from
Oct 15, 2024

Conversation

AlekseyTs
Copy link
Contributor

Related to #74275.

@AlekseyTs AlekseyTs requested a review from a team as a code owner October 9, 2024 01:34
@dotnet-issue-labeler dotnet-issue-labeler bot added the untriaged Issues and PRs which have not yet been triaged by a lead label Oct 9, 2024
@AlekseyTs
Copy link
Contributor Author

/azp run

Copy link

Azure Pipelines successfully started running 2 pipeline(s).

@AlekseyTs
Copy link
Contributor Author

@dotnet/roslyn-compiler Please review

1 similar comment
@AlekseyTs
Copy link
Contributor Author

@dotnet/roslyn-compiler Please review

@@ -78,117 +79,7 @@ Namespace Microsoft.CodeAnalysis.VisualBasic
'
' (2) For the built-in types, we can use .ToString(string format) for some format strings.
' Detect those cases that can be handled that way and take advantage of them.
Copy link
Member

@333fred 333fred Oct 11, 2024

Choose a reason for hiding this comment

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

Should we remove this comment now, since it's done in initial binding? Or mention that this transformation was done during initial binding and the result is in ConstructionOpt? #Resolved

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Should we remove this comment now, since it's done in initial binding? Or mention that this transformation was done during initial binding and the result is in ConstructionOpt?

I do not think there is a need to do either.

@AlekseyTs
Copy link
Contributor Author

@dotnet/roslyn-compiler For the second review

@jcouv
Copy link
Member

jcouv commented Oct 14, 2024

Looking

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 2)

@jcouv jcouv self-assigned this Oct 14, 2024
@AlekseyTs AlekseyTs merged commit 88c8ad9 into dotnet:main Oct 15, 2024
24 checks passed
@dotnet-policy-service dotnet-policy-service bot added this to the Next milestone Oct 15, 2024
@akhera99 akhera99 modified the milestones: Next, 17.13 P1 Oct 28, 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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants