A regression is the kernel not giving the same result with the same user space

Re:A regression is the kernel not giving the same result wit... by lmkg on Thursday November 02, 2017 @10:10AM (#15610513)

Rust also uses a sizable fraction of all publicly-available Rust code as a regression suite for compiler updates. This allows them to check edge cases that are "breaking in theory" to find out if there's actually any code that would be broken, or if the edge case had literally not yet been encountered.

[ Parent | on HN ]

Re:A regression is the kernel not giving the same result wit... by Cshelton on Thursday November 02, 2017 @10:15AM (#15610562)

By sizable fraction, he is referring to Cargo.io, Rust's public package repository.

They literally run all tests against every crate published to the package ecosystem. That is amazing.

[ Parent | on HN ]

Re:A regression is the kernel not giving the same result wit... by majewsky on Thursday November 02, 2017 @10:27AM (#15610661)

Makes you wonder why no-one else came up with that idea before. I mean, it is pretty revolutionary, but also really obvious in hindsight.

[ Parent | on HN ]

Re:A regression is the kernel not giving the same result wit... by taeric on Thursday November 02, 2017 @11:40AM (#15611377)

I'm curious why this is seen as a new idea. The capability to pull it off is somewhat new. In particular, at such a large scale.

But the idea is far from it. Commercial compilers probably had this more than open source ones in the past. Though, oddly, it was probably a weakness in some respects, since it almost certainly slowed feature development/releases.

[ Parent | on HN ]

Re:A regression is the kernel not giving the same result wit... by steveklabnik on Thursday November 02, 2017 @10:32AM (#15610718)

http://cpantesters.org/

[ Parent | on HN ]

Re:A regression is the kernel not giving the same result wit... by sevagh on Thursday November 02, 2017 @11:13AM (#15611128)

Crates.io

[ Parent | on HN ]