Thoughts on Rust, a few thousand lines in

Re:Thoughts on Rust, a few thousand lines in by vmarsy on Wednesday January 09, 2019 @08:17PM (#18870691)

I see, not very familiar with both those idioms `?` and `ok_or()?`

My current understanding is that those would return an Error only? I was more describing cases where you do want to return, but not necessarily return an `Error`.

For instance in a simplified example function that returns a boolean, you could decide to return `false`. is it possible there?

    // Function that returns a boolean value
    fn is_equal_to_ten(n: Option<u32>) -> bool {
        // some one liner  that checks for None, if it's not none, gives you `x` when `n` matches content of `Some(x)` (not real code): 
        if let Some(x) = n else { return false; /* what to do in case it's a None*/ } 
        
        // `x` is available here:
        return (x == 10);        
    }

Would this be considered bad practice in Rust?

[ Parent | on HN ]

Re:Thoughts on Rust, a few thousand lines in by steveklabnik on Wednesday January 09, 2019 @08:28PM (#18870747)

The question mark operator works via a trait, Try. Both Option and Result implement Try. If you use ? on a None value, it will return None, just like using ? on an Err returns an Err.

ok_or is a method on Option that would let you manually convert it to a Result. You could then combine it with ?, turning a None into a specific Err.

It won’t help for stuff that returns bool, it’s true.

[ Parent | on HN ]

Re:Thoughts on Rust, a few thousand lines in by vmarsy on Wednesday January 09, 2019 @08:33PM (#18870769)

Thanks for the detailed answer :)

[ Parent | on HN ]

Re:Thoughts on Rust, a few thousand lines in by Thiez on Thursday January 10, 2019 @06:44AM (#18873167)

Often such functions can be rewritten to perform some operations "inside" the option. For example:

    fn is_equal_to_ten(n: Option<u32>) -> bool {
        n.map(|n|n == 10).unwrap_or_default()
    }

[ Parent | on HN ]