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
I experimented a bit with running the tests on the JS backend, but I came to the conclusion that this is currently not viable. The problem is nim-lang/Nim#4714: 64 bit integers are broken on the JS backend, since they're implemented as floating point values.
We could use std/jsbigints on the JS backend, but I'd rather not do that, since it has a different API, which means we'd have to implement some functions twice. Apart from that, this library wouldn't be a pure Nim implementation anymore then.
The text was updated successfully, but these errors were encountered:
A possible (temporary) fix for this would be to use uint16/uint32 instead of uint32/uint64 on the JS backend. That should only require changing a few types and constants, which should be doable by placing some type aliases and consts in a when at the top.
I experimented a bit with running the tests on the JS backend, but I came to the conclusion that this is currently not viable. The problem is nim-lang/Nim#4714: 64 bit integers are broken on the JS backend, since they're implemented as floating point values.
We could use
std/jsbigints
on the JS backend, but I'd rather not do that, since it has a different API, which means we'd have to implement some functions twice. Apart from that, this library wouldn't be a pure Nim implementation anymore then.The text was updated successfully, but these errors were encountered: