From 71b6af4404bd43d937b24888b38705e9d73a7a58 Mon Sep 17 00:00:00 2001 From: Calvin Truong <46874161+cxtruong70@users.noreply.github.com> Date: Tue, 28 Jun 2022 18:45:53 -0700 Subject: [PATCH] Update README.md Elaborated on the meaning of Number.NEGATIVE_INFINITY and how it is represented as compared to representable floating point numbers. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 1e73b229..4801c941 100644 --- a/README.md +++ b/README.md @@ -476,7 +476,7 @@ Number.MIN_VALUE > 0; // -> true > `Number.MIN_VALUE` is `5e-324`, i.e. the smallest positive number that can be represented within float precision, i.e. that's as close as you can get to zero. It defines the best resolution that floats can give you. > -> Now the overall smallest value is `Number.NEGATIVE_INFINITY` although it's not really numeric in a strict sense. +> Now the overall smallest value is `Number.NEGATIVE_INFINITY` although it's not really numeric in a strict sense. Rather, unused permutations of the bits used to represent a floating point numbers are used to represent a number beyond the smallest representable floating point number. > > — [“Why is `0` less than `Number.MIN_VALUE` in JavaScript?”](https://stackoverflow.com/questions/26614728/why-is-0-less-than-number-min-value-in-javascript) at StackOverflow