We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
If we had one type for TrackedFloats, FT would be easier to use and maintain.
Question 1: instead of having N types for TrackedFloat (TrackedFloat16, ...), could we use one parameterized type?
TrackedFloat16
Question 2: if it's one type, do we lose anything important --- such as checks that a number never exceeds 32 bits? (Are those checks useful??)
The text was updated successfully, but these errors were encountered:
[Part of review for JuliaCon proceedings]
Is there any progress on this? This seems easy (ish) to implement and would improve flexibility (e.g. tracking of BigFloats would be possible).
BigFloat
Sorry, something went wrong.
Nope, no progress. We're looking for someone to take the lead on this project.
No branches or pull requests
If we had one type for TrackedFloats, FT would be easier to use and maintain.
Question 1: instead of having N types for TrackedFloat (
TrackedFloat16
, ...), could we use one parameterized type?Question 2: if it's one type, do we lose anything important --- such as checks that a number never exceeds 32 bits? (Are those checks useful??)
The text was updated successfully, but these errors were encountered: