He who sacrifices clarity for correctness deserves neither
-
-
Replying to @wycats
In cases where correctness matters, though, correctness is often *really hard to achieve*. As an extreme example, avionics software is unclear because they have to guarantee *every single line of code* matches a requirement. Should they sacrifice correctness for clarity?
1 reply 0 retweets 1 like -
Replying to @Hillelogram
In that case, it would be unclear to leave out those mission-critical requirements. The domain matters a lot -- be as clear as your domain of discourse requires.
2 replies 0 retweets 2 likes -
Replying to @wycats @Hillelogram
An example: For mission-critical software, Ruby/Python/JS are very *unclear* about critical aspects of the design. However, C sacrifices clarity for correctness and achieves neither. Rust is an attempt to be as clear as the requirements necessitate in those domains.
2 replies 0 retweets 2 likes
An example from a Rust RFC I wrote about times (https://github.com/rust-lang/rfcs/blob/master/text/1288-time-improvements.md#proposal …). .elapsed() is both clearer and more correct than attempts to compare two instants directly (RFC explains in more detail).
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.