blaming the language is not the way to approach this. if an engineer writes bad code that’s the engineers fault, not the languages.

this was bad code that should have never hit production, it is not a rust language issue.

echelon an hour ago | parent | next [-]

No. Don't say "you're holding it wrong". The language says "safe" on the tin. It advertises safety. This shouldn't be possible.

This is a null pointer. In Rust.

Unwrap needs to die. We should all fight to remove it.

	▲	aw1621107 an hour ago \| parent \| next [-]
		> The language says "safe" on the tin. It advertises safety. Rust advertises memory safety (and other closely related things, like no UB, data race safety, etc.). I don't think it's made any promises about hard guarantees of other kinds of safety.
	▲	dafelst an hour ago \| parent \| prev [-]
		panics are safe, what are you talking about? It is nothing like a null pointer.

anonnon an hour ago | parent | prev [-]

> blaming the language is not the way to approach this. if an engineer writes bad code that’s the engineers fault, not the languages.

A Rust zealot unironically typed this. I actually thought:

> the utter lack of self-awareness; this must be a troll

But doing some googling, it appears they're a TRUE and HONEST transgendered/nonbinary ("they/them pronouns"), anime avatar-using Rust zealot: