Cannot infer type even if specified.

[jD91mZM2]

So, I got the type annotations needed error. I tried everything. It refuses to work.

		let tmp: Result<NamedTempFile, ()> = NamedTempFile::new().map_err::<(), _>(|_: std::io::Error| ());
		let mut tmp: NamedTempFile = tmp?;

Error

(please don't tell me the code is stupid. I have a valid reason to ignore the error)

If this is my fault, and not an issue with Rust, apologies for spamming you with yet another false issue :(
I feel horrible

[retep998]

Could you provide the entire function for context? ? especially depends on the signature of the function it is in.

[jD91mZM2]

It's in a do catch without any variable assigning (do catch { ... };).

[Mark-Simulacrum]

Well, the whole function would also make it a little easier to see context in general -- right now, I can't even attempt to run this, which makes it hard to debug.

[jD91mZM2]

Oh, I'm sorry. Here it is. Ignore the unfinishedness of it. That's because it is. Unfinished. I'm trying to get rid of the play function and instead use a catch block.

[Mark-Simulacrum]

Is there a chance you could produce an example that doesn't rely on external crates? That makes debugging easier. If that's not possible, no worries.

[dsprenkels]

The following code triggers the same error on rustc 1.21.0-nightly (d692a91fa 2017-08-04):

#![feature(catch_expr)]

pub struct X;

pub fn new_x() -> Result<X, ()> {
    return Ok(X);
}

fn main() {
    do catch {
        let x: X = new_x()?;
        Ok(())
    };
}

(https://play.rust-lang.org/?gist=ffd0e7e68eb97486bf742bd63cc9cb2f&version=nightly)

[jD91mZM2]

@Mark-Simulacrum I have no idea why I didn't reply - probably forgot about it. I'm so sorry for being rude.

@dsprenkels Thanks!!

Seems like the problem is just in general returning a () error from do catch?

[dsprenkels]

I'm not really sure. The following code fails:

#![feature(catch_expr)]

fn main() {
    do catch {
        let x: () = Ok(())?;
        Ok(())
    };
}

But changing the return type does not seem to help. The following code also fails:

#![feature(catch_expr)]

fn main() {
    do catch {
        let x: () = Ok(())?;
        Ok(42)
    };
}

Note: the type of x also does not seem to matter.

[kennytm]

To fix it you need to give a type to the catch expression, not the let declaration. The problem is that it cannot infer the error type due to use of From in ?.

#![feature(catch_expr)]

pub struct X;

pub fn new_x() -> Result<X, ()> {
    return Ok(X);
}

fn main() {
    let _: Result<_, ()> = do catch {   // <---------
        let x: X = new_x()?;
        Ok(())
    };
}

The library should be able to instruct the inference engine to consider impl<T> From<T> for T as canonical impl, and choose that in case of ambiguity.

(And yes, the diagnostic is also an issue.)