which without application param now lists only executables#16895
Conversation
|
I've done some benchmarking and profiling. Tested on the same device on Linux and Windows. My config:
Results:
Current |
6aaf1b2 to
d3c09c8
Compare
|
With |
|
Please add some text that describes what this does in the release notes section so it can be mentioned in the next release's notes. |
Done |
|
This is what I'm seeing on Windows. Of course, all of this depends on how many files you have in your path and what type of hard drives you have in your machine. I'm fine with this. Thanks! Before❯ use std/bench *
❯ bench { which } --rounds 100
╭──────┬────────────────────────╮
│ mean │ 1sec 204ms 295µs 764ns │
│ min │ 1sec 170ms 6µs 800ns │
│ max │ 2sec 279ms 917µs 100ns │
│ std │ 108ms 936µs 393ns │
╰──────┴────────────────────────╯After❯ use std/bench *
❯ bench { which } --rounds 100
╭──────┬───────────────────╮
│ mean │ 276ms 41µs 368ns │
│ min │ 270ms 169µs 400ns │
│ max │ 360ms 372µs 200ns │
│ std │ 9ms 478µs 767ns │
╰──────┴───────────────────╯ |
Release notes summary - What our users need to know
The
whichcommand now filters files found in$PATHto include only executables.Tasks after submitting
Done:
Should resolve controversy in #16140