Unverified50% confidenceFactExact time
IEEE 754 double-precision floating point (float64) can only exactly represent fractions whose denominator is a power of 2, and decimal fractions like 0.1 and 0.2 are infinite repeating fractions in binary, so they are necessarily truncated when stored.
1
Sources
50%
Confidence
Long-term
Relevance
10/14/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedWhen billing by token, amounts should not be represented with floating point, because float64 cannot exactly represent decimal fractions in binary and the error accumulates and amplifies across millions of rows of data; the author uses Postgres NUMERIC, integer micro-units on the hot path, and decides the rounding level explicitly.74% similarUnverifiedThe IEEE 754 standard specifies five rounding modes: round to nearest even, round toward zero, round toward positive infinity, round toward negative infinity, and round to nearest away from zero.73% similarVerifiedFloating-point addition does not satisfy the associative law; (a+b)+c and a+(b+c) may yield different results under floating-point precision.68% similarUnverifiedDue to IEEE 754 floating-point precision limitations, directly using EXPECT_EQ for floating-point comparisons will almost certainly lead to false failures, and EXPECT_NEAR should be used to specify a tolerance.68% similarUnverifiedThe separation result generalizes to weighted fixed-count targets, as long as the weight ratios are bounded and the quota proportions are bounded away from 0 and 1, the separation holds even without permutation symmetry.65% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1025410API
curl https://kongchang.com/api/v1/knowledge/claims/1025410MCP
get_claim(id=1025410)