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
Type conversions not according to documentation #25
Comments
let's fix the docs and generally support implicit conversions to a float instead of a number since it's more efficient and let users use numbers only explicitly since they're expensive |
These should be explained somehow as well:
|
And perhaps it should be noted in docs even more that simple use cases like |
@tethal the issue with the excess output is a result of the rounding heuristic - maybe we should try to improve the algorithm; current it requires 9 or 15 consecutive |
docs have been corrected |
According to documentation, strings should be converted to numbers, but they seem to be converted to floats:
(Tested with version 0.8.12, git hash: 2ee5c95)
The text was updated successfully, but these errors were encountered: