Skip to content

Fix string.Split handling of trimming with no replacements - #73234

Merged
stephentoub merged 1 commit into
dotnet:mainfrom
stephentoub:fixsplit
Aug 5, 2022
Merged

stephentoub merged 1 commit into
dotnet:mainfrom
stephentoub:fixsplit

Conversation

@stephentoub

Copy link
Copy Markdown
Member

Fixes #73194

@ghost

ghost commented Aug 2, 2022

Copy link
Copy Markdown

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

@ghost

ghost commented Aug 2, 2022

Copy link
Copy Markdown

Tagging subscribers to this area: @dotnet/area-system-runtime
See info in area-owners.md if you want to be subscribed.

Issue Details

Fixes #73194

Author: stephentoub
Assignees: stephentoub
Labels:

area-System.Runtime

Milestone: -

@stephentoub
stephentoub merged commit b1a309d into dotnet:main Aug 5, 2022
@stephentoub
stephentoub deleted the fixsplit branch August 5, 2022 20:16
@ghost ghost locked as resolved and limited conversation to collaborators Sep 5, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

string.Split not working as expected when using multiple string separators and StringSplitOptions.TrimEntries

4 participants