-
Notifications
You must be signed in to change notification settings - Fork 19
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
Incompatibility warnings #4
Comments
Maybe it should be under a |
Easiest/best way would prob be to add a more where it force uses the JS bindings so you can see what breaks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Using sodium-universal is for people that don't want to concern themselves with platform incompatibilities (one system to work with all). As such I think it would be good for developers to have a means of using sodium-universal that also highlights if they are using something that doesn't work for some platforms. Something like:
will run following in console:
This way a person could easily see what the progress is and that the application they are building is currently not as compatible as they may think it is.
In a future step I could imagine that in a future release that supports
crypto_stream_xchacha20
it could warn the other way around:I think it would be reasonable to add this to the library (including all the issues on github). Would you be okay with PR's that add this?
The text was updated successfully, but these errors were encountered: