You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 5, 2024. It is now read-only.
I wonder if it'd be useful to have a feature unsafe-optimizations that turns on unsafe code with the only intention to optimize. Currently the candidate is using [MaybeUninit<u8>; 65] inside SerializedPublicKey. Relies on correct impl in secp256k1 ofc but that one already calls memset on the whole array 🙈
The text was updated successfully, but these errors were encountered:
I wonder if it'd be useful to have a feature
unsafe-optimizations
that turns onunsafe
code with the only intention to optimize. Currently the candidate is using[MaybeUninit<u8>; 65]
insideSerializedPublicKey
. Relies on correct impl insecp256k1
ofc but that one already calls memset on the whole array 🙈The text was updated successfully, but these errors were encountered: