-
Notifications
You must be signed in to change notification settings - Fork 911
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
[experimental] Use optimized base16 encode strategy #2527
Comments
Are you interested in fixing this one too @arobsn? |
@steveluscher i did push a pr for this Issue, but i m unsure how we can test it |
i m not reffering to the correctness of the code, but rather to the improve in speed |
* fix #2527 * base16 encode benchmark * fix pnpx vs pnpm exec * Performance and code compactness nits * Run `style:fix` --------- Co-authored-by: steveluscher <me+github@steveluscher.com>
* fix #2527 * base16 encode benchmark * fix pnpx vs pnpm exec * Performance and code compactness nits * Run `style:fix` --------- Co-authored-by: steveluscher <me+github@steveluscher.com>
Oh, didn't see the notification, sorry. Happy you guys have this fixed now :) |
🎉 This issue has been resolved in version 1.91.8 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Because there has been no activity on this issue for 7 days since it was closed, it has been automatically locked. Please open a new issue if it requires a follow up. |
This is apparently way faster than what we're doing here: paulmillr/noble-curves#83
The text was updated successfully, but these errors were encountered: