-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Remove duplicate code for processing arrays vs strings #79233
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
Remove duplicate code for processing arrays vs strings #79233
Conversation
|
@dotnet/roslyn-compiler this is ready for review. |
RikkiGibson
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
everything LGTM but want to get the insertion unblocked first and ideally a test insertion for this as it seems this area has been very sensitive to changes.
SGTM> |
RikkiGibson
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR changes LGTM
|
@dibarbet for visibility |
Followup to #79232
With the spannificaiton of most low level char-segment handling routines, we can now just have the string paths directly call into those routines with spans.