News for hackers. Stuff that matters.
Re:Mercurial 4.0 Sprint Notes by jjnoakes on Wednesday October 19, 2016 @09:32AM (#12743575)
> SQLite is not a good project to mention rewriting

Which, as I said, is not what I'm doing. I'm only disagreeing with the premise that 100% test coverage means 0% chance of an unsafe bug existing in the code base (for any code base, not just for SQLite).

Re:Mercurial 4.0 Sprint Notes by cyphar on Wednesday October 19, 2016 @10:05PM (#12749357)
Personally, I consider 100% branch coverage to mean an effectively 0% chance of an unsafe bug existing in the code base. Does Rust have 100% branch coverage in their compiler? So how can you be absolutely sure their compiler doesn't have bugs when doing borrow checking and other tomfoolery? 100% branch coverage is an _insanely_ high standard and you can't compare it to any other project unless that project also has 100% branch coverage or similar.