Hacker News Reader

Comment by bla2 | Hacker News Reader

More like "this is why we should use LLVM's libFuzzer or similar". Apple is just not doing basic code hygiene stuff here.

View on HN

Apple has been known to fuzz their code. Just because they didn't uncover this particular bug doesn't mean they didn't do any fuzzing, it just means the fuzzing didn't hit this case.

Fuzzing finds bugs, using a safe language precludes them.

No it doesn't. At best it precludes a certain class of bugs (which may be very significant, but it's not a silver bullet)

var stack = [];

function ThisWillNeverCrash() {

   console.log('hello');

   stack.push('it');

   setTimeout(ThisWillNeverCrash, 0);

}

setTimeout(ThisWillNeverCrash, 0);

// my point in posting this was to demonstrate a bug ... that array will eventually run out of memory and this loops infinitely but not using a standard language loop construct... but I see someone didn’t think that was relevant

What constitutes a safe language? Is Rust safe?

Not by the parent's definition, anyway. Rust code certainly has bugs; I know, I've written some!

Now, if they're talking about memory safety bugs...

Reply on news.ycombinator.com