-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Load include_bytes! directly into an Lrc #115296
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
r? @jackh726 (rustbot has picked a reviewer for you, use r? to override) |
This comment has been minimized.
This comment has been minimized.
8f3f92c
to
2f0946d
Compare
This comment has been minimized.
This comment has been minimized.
2f0946d
to
f26293d
Compare
@bors r+ |
Based on searching the benchmark suite I suspect this won't have any observable perf impact, but the point is to make things faster... @bors rollup=iffy |
☀️ Test successful - checks-actions |
Finished benchmarking commit (41cb42a): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 632.239s -> 631.418s (-0.13%) |
This PR deletes an innocent-looking
.into()
that was converting from aVec<u8>
toLrc<[u8]>
. This has significant runtime and memory overhead when usinginclude_bytes!
to pull in a large binary file.