Repository navigation
feat: also record peak memory with hyperfine 2 - #18
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
JoshuaKGoldberg
commented
Oct 8, 2026
JoshuaKGoldberg
commented
Oct 8, 2026
Co-authored-by: Josh Ghoulberg 👻 <github@joshuakgoldberg.com>
JoshuaKGoldberg
marked this pull request as ready for review
October 8, 2026 14:05
|
@all-contributors please add joshuakgoldberg for code.
|
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.
PR Checklist
status: accepting prsOverview
Bumps the expected hyperfine to 2.0.0 so
npm run measurerecords peak memory alongside wall-clock time, reading hyperfine's new JSON export schema.Memory columns are skipped on Windows, where hyperfine doesn't support memory measurements.
💖