0.30000000000000004
json
0.30000000000000004 | json | |
---|---|---|
245 | 41 | |
1,410 | 4,591 | |
- | 1.2% | |
2.0 | 8.7 | |
2 months ago | 14 days ago | |
CSS | Rust | |
GNU General Public License v3.0 only | Apache License 2.0 |
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.
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/
json
-
What even is a JSON number?
Oh wow. So serde_json doesn't roundtrip floats by default, it uses some imprecise faster algorithm https://github.com/serde-rs/json/issues/707
Good thing there's msgpack I guess.
-
I pre-released my project "json-responder" written in Rust
tokio / hyper / toml / serde / serde_json / json5 / console
-
Flow Updater JSON Creator
Serde JSON, an extension of the serde crate that enables the serialization and deserialization of Rust structs.
-
A Simple CRUD API in Rust with Cloudflare Workers, Cloudflare KV, and the Rust Router
To serialize and deserialize data, we'll employ the popular serde crate along with serde_json. This will allow us to easily convert between Rust types and JSON when working with API requests and responses. For async operations we'll use the Rust futures crate.
- Rust devs push back as Serde project ships precompiled binaries
-
Building a Rust app with Perseus
From the Cargo.toml file above, we can see that the Perseus version at the time of publication is 0.4.2 and has the following dependencies that are common to both the engine side (server-side) and client side of a Perseus application: sycamore, serde, and serde_json.
-
REST API in RUST with ntex
serde_json
-
Müsli - An experimental binary serialization framework with more choice
Number parsing uses a fairly naive but uses a lossless algorithm in musli-json. In serde_json they use a fork of lexical I haven't wrapped my head around. I wanted something simple to start with.
-
How can I deserialise this value?
Your best best would be to use an enum. Either your own or something like the one from serde_json depending on what you are trying to do.
-
Spotting and Avoiding Heap Fragmentation in Rust Apps
Don't do that if you care about memory usage. In your toy program, I wouldn't be surprised if memory usage was a lot better if you used Box instead. (even if it doesn't look like it, you can handle almost all the use cases of serde_json::Value with it, often not much less convenient)
What are some alternatives?
glibc - Unofficial mirror of sourceware glibc repository. Updated daily.
serde - Serialization framework for Rust
gcc
json-rust - JSON implementation in Rust
v8.dev - The source code of v8.dev, the official website of the V8 project.
hjson-rust for serde - Hjson for Rust
proposal-decimal - Built-in decimal datatype in JavaScript
pikkr - JSON parser which picks up values directly without performing tokenization in Rust
import-maps - How to control the behavior of JavaScript imports
serde-yaml - Strongly typed YAML library for Rust
media
RapidJSON - A fast JSON parser/generator for C++ with both SAX/DOM style API