Parse-Error: new-line in string interpolation expressions#50799
Closed
bernd5 wants to merge 3 commits intodotnet:masterfrom
bernd5:master
Closed
Parse-Error: new-line in string interpolation expressions#50799bernd5 wants to merge 3 commits intodotnet:masterfrom bernd5:master
bernd5 wants to merge 3 commits intodotnet:masterfrom
bernd5:master
Conversation
Member
|
The C# specification does not allow this today. https://github.com/dotnet/csharplang/blob/master/spec/lexical-structure.md#interpolated-string-literals The grammar explicitly forbids newlines in the |
Contributor
Author
|
Implemented via #56853 |
bernd5
added a commit
to bernd5/roslyn
that referenced
this pull request
Nov 13, 2021
… implemented as part of dotnet#50799 and later realized via dotnet#56853
333fred
pushed a commit
that referenced
this pull request
Dec 13, 2021
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See: #50742