Hacker Newsnew | past | comments | ask | show | jobs | submit | mbrubeck's commentslogin

There's some active work recently on fixing blocking issues, e.g.:

https://github.com/rust-lang/rust/pull/148725

https://github.com/rust-lang/rust/pull/149489


So first you say it has always cost this much, but in the next breath you say that its cost has outpaced a high rate of inflation. Mathematically, these can't both be true.


A) Inflation in healthcare costs is well documented and unrivaled

B) Biden papered over A) with "temporary" covid subsidies in 2021 and those are going away, revealing A) again


> two equal numbers divided by themselves equal 1

That's not true. For example: 0 == 0, but 0/0 != 1.

(See also +Infinity, -Infinity, and -0.)


If you're going to nitpick this comment, you should note that infinity isn't on the number line and infinity != infinity, and dividing by zero is undefined


We're commenting on an article about IEEE 754 floating point values. Following the IEEE 754 standard, we have:

    >> isNaN(Infinity)
    false
    >> Infinity == Infinity
    true
    >> Infinity / Infinity == 1
    false

    >> isNaN(0)
    false
    >> 0 == 0
    true
    >> 0 / 0 == 1
    false
Also, you say NaN ("not a number") is "defined as a number" but Infinity is not. I would think every IEEE 754 value is either "a number" or "not a number". But apparently you believe NaN is both and Infinity is neither?

And you say 0 / 0 is "undefined" but the standard requires it to be NaN, which you say is "defined".


From over a decade ago, a paper on then-commercially-available browser fingerprinting tech, including a study of its deployment in the wild:

https://dl.acm.org/doi/10.1109/SP.2013.43 Nick Nikiforakis, Alexandros Kapravelos, Wouter Joosen, Christopher Kruegel, Frank Piessens, and Giovanni Vigna. 2013. Cookieless Monster: Exploring the Ecosystem of Web-Based Device Fingerprinting. In Proceedings of the 2013 IEEE Symposium on Security and Privacy (SP ’13).


Automatic garbage collection of old build artifacts* is coming in Rust 1.88 (currently on the beta channel, will become the new stable release in two weeks):

https://github.com/rust-lang/cargo/issues/12633

*EDIT: For now this only deletes old cached downloads, not build artifacts. Thanks epage for the correction below.


That is not for build artifacts but global caches like for `.crate` files but its a stepping stone.


Oops, thanks for the correction.


That’s as an additional flag and not the default?


In versions earlier than 1.88, garbage collection required the unstable -Zgc flag (and a nightly toolchain). But in 1.88 and later, automatic garbage collection is enabled by default.


In both of those cases the designated entity was incorporated in the US (KindHearts in Ohio, AHIF-Oregon in Oregon).


In words like icône in French, ô is typically used where the original Greek uses ω (omega).

https://en.wikipedia.org/wiki/Circumflex_in_French#Indicatio...


units.txt defines `water` like this:

    water := gram / cm^3     // Standard density of water (defined)
1 g/cm^3 is the maximum density of water at standard pressure (1 atm), which it reaches at 3.98°C.

(Or at least, that used to be true by definition. Using the current definition of the kilogram, and the latest measurements of water density, the maximum density is actually closer to 0.99997 g/cm^3.)


I see, that makes sense now.


Looks like the author has fixed that; it’s now available under the Apache License 2.0.


Since krep doesn’t support regular expressions, it can’t run most of the ripgrep benchmark suite.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: