3 ms·
You could have done that in Rust but you wouldn't, because the allure of just typing a single character of ? is too strong. The UX is terrible — the path
by Mawr 11mo ago
You could have done that in Rust but you wouldn't, because the allure of just typing a single character of
?
is too strong.
The UX is terrible — the path of least resistance is that of laziness. You should be forced to provide an error message, i.e.
?("failed to create file: {e}")
should be the only valid form.
In Go, for one reason or another, it's standard to provide error context; it's not typical at all to just return a bare `err` — it's frowned upon and unidiomatic.
- nu11ptr 11mo ago> You could have done that in Rust but you wouldn't, because the allure of just typing a single character of ? is too strong. You could have done that in Go but you wouldn't, because the allure of just typing two words return err is too strong. Quite literally the same thing and the only difference is bias and habit.