Non-allocating YieldSpec::try_from_str #31286
Merged
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
Change `try_from_str` to not allocate. No behavior change, just noticed this looking at related code. Signed-off-by: Moritz Hoffmann <[email protected]>
antiguru
force-pushed
the
linear_join_spec_no_alloc
branch
from
4d0797f to
d7f7dc1
Compare
teskje
approved these changes
Feb 4, 2025
| ["work", amount] => { | ||
| let mut iter = option.split(':').map(|p| p.trim()); | ||
| let parts : [_; 3]= std::array::from_fn(|_| iter.next()); | ||
| match parts { |
There was a problem hiding this comment.
Would match (iter.next(), iter.next(), iter.next()) { ... } also work?
There was a problem hiding this comment.
Yes, but I figured we can inline parts, that's even less code :)
Signed-off-by: Moritz Hoffmann <[email protected]>
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.
Change
try_from_strto not allocate. No behavior change, just noticed this looking at related code.Checklist
$T ⇔ Proto$Tmapping (possibly in a backwards-incompatible way), then it is tagged with aT-protolabel.