Constant new SmallVec<T, N> for arrays smaller than N#377
Merged
Conversation
Collaborator
|
This fails to build in Rust 1.57, so we will need to bump our MSRV if we want to ship this. It looks like it might require Rust 1.83? (Also, I'm not sure why this made it through the merge queue without passing all of the tests. Looks like we need to fix our merge queue configuration.) |
Merged
|
@otcova thank you so much for this PR. It made our code 5-10% faster on a bunch of benchmarks because we frequently create SmallVec with one element and the compiler is able to make much better code with this. |
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.
What is this about
We should be able to create a constant SmallVec<T, N> of any size from 0 to N.
Currently, we have the following:
This PR
I've implemented a new
from_bufthat takes an array of size [T; S] instead of [T; N].Does it conflict with the current
from_buf?If we move it to a different function and keep the current
from_bufhow it is now, it's fine for me.Performance concerns
I've copied the code into https://godbolt.org to check that the compiler is able to optimize the copy into a new buffer.
Here are the results:
Assembly with
-C opt-level=1: