> but Rust's type system did catch this error - and then author decided it's fin... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		samdoesnothing 6 months ago \| parent \| context \| favorite \| on: Cloudflare outage on November 18, 2025 post mortem > but Rust's type system did catch this error - and then author decided it's fine to panic if this error happens The issue is that it wasn't fine to panic, thus Rust did not catch this error.

yoyohello13 6 months ago [–]

Come on now. You can't blame the compiler when the programmer explicitly told the compiler to not worry about it. There is nothing in existence that can protect against something like that.

samdoesnothing 6 months ago | [–]

I'm not blaming the compiler, of course programmers can explicitly write incorrect code in any language. It's not Rust's fault.

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