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.

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

Posit floating point support (HAST-136) #21

Open
Piedone opened this issue Oct 16, 2017 · 3 comments
Open

Posit floating point support (HAST-136) #21

Piedone opened this issue Oct 16, 2017 · 3 comments
Assignees

Comments

@Piedone
Copy link
Member

Piedone commented Oct 16, 2017

Posit is a floating point number type that's better than the usual IEEE floats but can be easily used as a drop-in replacement still. Let's see this instead of Unum.

See the sources below here: https://github.com/libcg/bfp

Let's create a generally usable .NET library which is transformable with Hastlayer.

This was referenced Oct 21, 2017
@Piedone
Copy link
Member Author

Piedone commented Dec 18, 2017

Posit work ongoing in this repo, on this branch: https://github.com/Lombiq/Arithmetics/tree/issue/HAST-136

@antonfirsov
Copy link

I don't think it's worth the efforts at this point.
Feels like a rabbit hole: exciting, but maybe less critical from the POV of product adoption rates. Most of the now-realistic scenarios could be managed using basic fixed-point math.

@Piedone
Copy link
Member Author

Piedone commented Feb 14, 2018

Since it's also a good thorough test of Hastlayer itself we've mostly completed it (the results including a lot of bugs fixed in Hastlayer, and support for method inlining added).

Nevertheless fixed-point will indeed be the most efficient choice every time (with floating point only to be used if you specifically need floating point, not just the ability to use fractions) and apart from handling this with integers you can also do this with the built-in Fix64 type.

@Piedone Piedone changed the title Posit floating point support Posit floating point support (HAST-136) Sep 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants