It doesn't only WARN about ignoring an error, it refuses to compile. T and Result<T, E> are different types.
The warning comes if you try to call a function for its side effects and ignore the return value. In most cases it’s fine, but ignoring a Result or a Future will issue a warning.
I've always wondered whether "unwrap"-ing is considered ignoring? I personally always equated it to ignoring if there's an error
Re:Go vs. Rust: Writing a CLI Tool
by steveklabnik on Tuesday August 04, 2020 @10:40AM
(#24050450)
I would say no, because it's not ignored. It makes it explode.
- it warns you if you ignore an error. - it forces variables and fields to be initialized. - it has sum types and generics instead of interface{}. - it prevents some race conditions at compile time. - it pushes programmers towards immutability.