-
-
Notifications
You must be signed in to change notification settings - Fork 14.2k
join_path_syms_lazy
#149936
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
base: main
Are you sure you want to change the base?
join_path_syms_lazy
#149936
Conversation
|
rustbot has assigned @GuillaumeGomez. Use |
|
Sorry, didn't mean to mark this as ready to review, no need to review yet @GuillaumeGomez |
|
Gonna (finally) go to sleep, and CI hasn't failed yet, so I'll trigger a perf run in the meantime. @bors try @rust-timer queue profiles=Doc |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
…try> `join_path_syms_lazy`
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (8b5f0cd): comparison URL. Overall result: ❌ regressions - no action neededBenchmarking this pull request means it may be perf-sensitive – we'll automatically label it not fit for rolling up. You can override this, but we strongly advise not to, due to possible changes in compiler perf. @bors rollup=never Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)This benchmark run did not return any relevant results for this metric. CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 475.622s -> 477.006s (0.29%) |
| path.iter() | ||
| .copied() | ||
| .map(|seg| Some(seg).filter(|seg| *seg != kw::PathRoot).maybe_display()) | ||
| .joined("::", f) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not using intersperse instead?
Unrelated to, but inspired by, #149915 .
Let's see what this does to perf