Gabriel Schneider - גבריאל שניידרDec 6
artemist

Your Rust unwrapped:

thread 'main' (1087627) panicked at src/main.rs:2025:12:
called `Option::unwrap()` on a `None` value
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Dec 5 at 6:10pmWeb
Show threadmx alex tax1a - 2020 (6)Dec 5
@artemist we truly do not understand how rust people wind up in that situation, like, the ENTIRE POINT of nullable types is that you can Not Do This
Show threadCeri   Dec 5
@atax1a @artemist i remember when i was learning rust a lot of tutorials go "we'll use unwrap() to get it working", its a bit of a bad habit. Although ive found it easier to just handle those types properly ​​ doing it later is a lot of refactoring
Show threadmx alex tax1a - 2020 (6)Dec 5
@miawgogo @artemist basically all of the ocaml tutorials we've seen say something to the effect of "never use the Option function that throw"
Show threadlonjilDec 7

@atax1a @artemist if the none case violates a precondition needed by the program, crashing is sensible and safe.

Libraries ought to avoid it, though.