# Computation precision with Float

**URL:** <https://discourse.julialang.org/t/computation-precision-with-float/91180>\
**Category:** General Usage\
**Tags:** precision\
**Created:** [December 3, 2022, 3:11pm UTC](https://discourse.julialang.org/t/computation-precision-with-float/91180 "2022-12-03T15:11:09Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![John\_Gibson](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/john_gibson/32/5321_2.png) [@John\_Gibson](https://discourse.julialang.org/u/John_Gibson)\
**Post date:** [December 3, 2022, 7:18pm UTC](https://discourse.julialang.org/t/computation-precision-with-float/91180/8 "2022-12-03T19:18:48Z")

</div>

A brief overview of the issues:

> [@PSA: floating-point arithmetic](https://discourse.julialang.org/t/psa-floating-point-arithmetic/8678):
>
> Sometimes people are surprised by the results of floating-point calculations such as julia\> 5/6 0.8333333333333334 # shouldn't the last digit be 3? julia\> 2.6 - 0.7 - 1.9 2.220446049250313e-16 # shouldn't the answer be 0? These are not bugs in Julia. They’re consequences of the IEEE-standard 64-bit binary representation of floating-point numbers that is burned into computer hardware, which Julia and many other languages use by default. Brief explanation You can t…

---

_[View the full topic](https://discourse.julialang.org/t/computation-precision-with-float/91180)._