News for hackers. Stuff that matters.
Re:Four limitations of Rust's borrow checker by unshavedyak on Tuesday December 24, 2024 @10:26PM (#42506630)
Yea, but that's my argument - that they're being dense (i imagine on purpose?). The phrase doesn't mean that nothing can fail at runtime. Of course it doesn't.

Rather that we have many tools to write a program that can be written with many compile time checks. For example many representations of state can be describe in compile time checks via enums, type transitions, etc.

Re:Four limitations of Rust's borrow checker by brabel on Wednesday December 25, 2024 @03:19AM (#42507651)
> The phrase doesn't mean that nothing can fail at runtime.

That's exactly what that phrase means, you're twisting the actual words in the phrase to be able to arrive at something more acceptable in your own mind. All you're saying is "oh you shouldn't take it literally". I can guarantee most people take that literally and it's bullshit.

Re:Four limitations of Rust's borrow checker by unshavedyak on Wednesday December 25, 2024 @10:10AM (#42509141)
So you think everyone using that phrase thinks it's not possible to fail at all at runtime, in any manner?

Unsafe, Panic and Error would like a word.