performance take1: use array access for non multibyte string offsets #43
Conversation
This file contains 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
staabm
commented
Mar 20, 2021
| @@ -39,7 +39,12 @@ public function take1(): TakeResult | |||
| { | |||
| $this->guardEndOfStream(); | |||
|
|
|||
| $token = mb_substr($this->string, 0, 1); | |||
| $ord = \ord($this->string[0]); | |||
There was a problem hiding this comment.
in case we would have a non-multibyte-StringStream in which the ord-call would not be necessary (because multi byte strings dont need to be supported), a $this->string[0] would be way faster then a substr($this->string, 0, 1);
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.
this didn't worked out as I initially thought.. for discussion and maybe inspiration purposes I figured it might still be usefull to open a PR