# Posits - a new approach could sink floating point computation

**URL:** <https://discourse.julialang.org/t/posits-a-new-approach-could-sink-floating-point-computation/26176>\
**Category:** Numerics\
**Created:** [July 9, 2019, 8:02am UTC](https://discourse.julialang.org/t/posits-a-new-approach-could-sink-floating-point-computation/26176 "2019-07-09T08:02:41Z")\
**Posts on this page:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![simonbyrne](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/simonbyrne/32/19_2.png) [@simonbyrne](https://discourse.julialang.org/u/simonbyrne)\
**Post date:** [July 10, 2019, 4:27pm UTC](https://discourse.julialang.org/t/posits-a-new-approach-could-sink-floating-point-computation/26176/17 "2019-07-10T16:27:36Z")

</div>

I think posits are an interesting idea, but I’m somewhat skeptical: a lot of the examples proposed by Gustafson seem a little too convenient, or rely on arguments appealing to a sufficiently smart compiler to do various stability transformations. I think more real-world test cases like @milankl’s are useful to identify the exact benefits.

Two interesting articles on posits I’ve liked quite liked are:

- [posit: thin triangle other tricks (REVEALED!)](https://marc-b-reynolds.github.io/math/2019/02/06/Posit1.html)
- [Posits: the good, the bad and the ugly - Inria](https://hal.inria.fr/hal-01959581v4)

---

_[View the full topic](https://discourse.julialang.org/t/posits-a-new-approach-could-sink-floating-point-computation/26176)._