rust•armanriazi•unwrap

ArmanRiazi answered on March 8, 2022 Popularity 2/10 Helpfulness 1/10

answer rust•armanriazi•unwrap

rust•armanriazi•unwrap

Comment

Calling .unwrap() on a Result is often considered poor style. When called on an error type, the program crashes without a helpful error message.
{
It would also be appropriate to call unwrap when you have some other logic that ensures the Result will have an Ok value, but the logic isn’t something the compiler understands. You’ll still have a Result value that you need to handle: whatever operation you’re calling still has the possibility of failing in general, even though it’s logically impossible in your particular situation. If you can ensure by manually inspecting the code that you’ll never have an Err variant, it’s perfectly acceptable to call unwrap. Here’s an example:


fn main() {
    use std::net::IpAddr;

    let home: IpAddr = "127.0.0.1".parse().unwrap();
}
}

Popularity 2/10 Helpfulness 1/10 Language rust

Source: github.com

Tags: rust

Link to this answer
Share Copy Link

Contributed on Mar 08 2022

ArmanRiazi

0 Answers Avg Quality 2/10

rust•armanriazi•unwrap

Contents

More Related Answers

rust•armanriazi•unwrap

Grepper

Documentation

Social

Legal

Contact

Oops, You will need to install Grepper and log-in to perform this action.