Remove begin() caching based on advice from Tim Song#170
Merged
Conversation
tzlaine
reviewed
Dec 16, 2025
| given category in constant time (amortized)." This means that we should be making the | ||
| assumption that the underlying iterator operations used by `begin()` are "amortized | ||
| constant time" (in a hand-wavey sense). Tim also pointed out that transcoding from UTF is | ||
| equivalent to `views::adjacent<4>`, which doesn't cache. |
Collaborator
There was a problem hiding this comment.
This is very interesting. Does this mean that to_utfN will again be borrowable?
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
3 participants
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.
No description provided.