Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Handling of BigFloats/BigInts #25

Open
simonbyrne opened this issue Sep 6, 2019 · 1 comment
Open

Handling of BigFloats/BigInts #25

simonbyrne opened this issue Sep 6, 2019 · 1 comment

Comments

@simonbyrne
Copy link
Member

Currently arbitrary precision values are represented by WReal and WInteger types, which are basically string representations. Should we automatically convert these to BigFloat/BigInts? The main downside is the additional overhead of parsing, and the potentially lossy binary/decimal conversion in the case of WReal.
@BeastyBlacksmith
Copy link
Contributor

For me it would be okay to be explicit, if I want BigFloat/Int precision. Other people may feel different.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@simonbyrne @BeastyBlacksmith