Use .IndexOf(char/byte) where possible#9539
Merged
Merged
Conversation
Member
|
|
Member
Author
I think I'm going to back that out as its too ugly; and the current version shouldn't be too bad, even if its doing extra work. |
Member
Author
|
K, dropped the Formreader change |
Tratcher
approved these changes
Apr 19, 2019
Contributor
|
Looks nice and safe to me. I'll merge now for preview 5. |
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.
As its faster. Also string.IndexOf(string) is by default CurrentCulture so its much faster than that.
Follow up to #9537
FormPipeReader goes a bit ugly using the ternaries
/cc @GrabYourPitchforks for more spice