-
Notifications
You must be signed in to change notification settings - Fork 624
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
Remove JavaScript versions of std/hash #658
Comments
That would be a breaking change, but it feels like one we should take, before it gets too late. As far as single algorithm imports, it isn't necessary, in my opinion to preserve. It was the nature of the way they were being built up versus intentional design. Having a single API is better. It maybe worth looking at the single API as a whole though... In particular the An interim step could be to just gut the standalone ones. They have things like |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@bartlomieju, is this able to be closed? |
Right now we're doubling up on a lot of hashing algorithms.
The WebAssembly implementation is a good first pass but if we're keeping single algorithm imports (e.g std/hash/sha1.ts) then we should probably generate WebAssembly backed classes for these as-well.
The text was updated successfully, but these errors were encountered: