SoftFloat-3a
0.30000000000000004
| SoftFloat-3a | 0.30000000000000004 | |
|---|---|---|
| 1 | 245 | |
| 8 | 1,405 | |
| - | - | |
| 10.0 | 2.0 | |
| about 5 years ago | about 1 month ago | |
| C | CSS | |
| GNU General Public License v3.0 or later | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
SoftFloat-3a
0.30000000000000004
-
What even is a JSON number?
https://0.30000000000000004.com/
Although it would be good to move in the direction of using a BigDecimal equivalent by default when ingesting unknown data.
- Floating Point Math
-
Working with Numpy floats and Forex financial instruments
There's no such thing as precision for floats. Floating-point calculations are always inaccurate: read this: https://0.30000000000000004.com/
- Just learned the difference between decimal and float
-
how do i make the decimals not fucked up
Edit: This specific example even has its own website: https://0.30000000000000004.com/
- why doest this loop ever terminate?
-
Decoding Why 0.6 + 0.3 = 0.8999999999999999 in JS and How to Solve?
In everyday math, we know adding 0.6 + 0.3 equals 0.9, right? But when we turn to computers it results in 0.8999999999999999. Surprisingly, this doesn’t just happen only in JavaScript; it’s the same in many programming languages like Python, Java, C too. Also, it’s not just about this specific calculation. There are many more decimal calculations showing similar not-quite-right answers.
- Lies My Calculator and Computer Told Me [pdf]
-
64-Bit Bank Balances ‘Ought to Be Enough for Anybody’?
Surprisingly common values like 0.1 don't have a precise representation in binary for most formats, including standard floating point number formats. See https://0.30000000000000004.com/ for more detail than you can shake a stick at.
Also if the local tax code states using 5 decimal places for intermediate values when you will introduce “errors” using formats that give greater precision as well as those that give less precision. Having work on mortgage and pension calculations I can state that the (very) small errors seen at individual steps because of this can balloon significantly through repeated calculations.
Furthmore, the name floating point gives away the other issue. Floating point numbers are accurate to a given number of significant figures not decimal places. For large numbers any decimal places you have in the result are at best an estimate, and as above any rounding errors at each stage can compound into a much larger error by the end of a calculation.
-
I don't get these people
You'll love this https://0.30000000000000004.com/
What are some alternatives?
gcc
glibc - Unofficial mirror of sourceware glibc repository. Updated daily.
v8.dev - The source code of v8.dev, the official website of the V8 project.
proposal-decimal - Built-in decimal datatype in JavaScript
import-maps - How to control the behavior of JavaScript imports
media
book - The Rust Programming Language
asdf - Extendable version manager with support for Ruby, Node.js, Elixir, Erlang & more
proposal-types-as-comments - ECMAScript proposal for type syntax that is erased - Stage 1 [Moved to: https://github.com/tc39/proposal-type-annotations]
FixedPointNumbers.jl - fixed point types for julia
Boost.Multiprecision - Boost.Multiprecision