-
Notifications
You must be signed in to change notification settings - Fork 153
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
RFC: parseBase/toString for radixes outside 2/10/16 (maybe even 8) #107
Comments
I think it should probably work for any bases from 1 to 36 as for regular JS numbers. |
IMO, user supplied alphabet does not make sense, never heard about this sort of API in any serious big number library. |
I assume you are aware that the alphabet varies between big number libraries.
|
Ok, I was a bit wrong then. Anyway, I don't feel like it is justified. Performance-wise it will mean a lot slower code. 3rd-party libraries could take |
Sorry, closing the issue. |
Does any other base than 2/10/16 (and maybe even 8) make any sense in day to day usage? Is there any use case for them today? The current implementation forces a single hardcoded alphabet consisting of 0-9,a-z,A-Z cut off at the radix.
Wouldn't it make more sense for those to support a user-supplied alphabet, similarly to the way base-x does it?
The text was updated successfully, but these errors were encountered: