Sounds good! I'm not sure this is the right place for a code action though as most the time you don't want to use case, and there's an action for expanding case

Could this apply the other way round too? For example:

fn fallible(value: String) -> Result(Int, Nil) {
  case value {
    "1" -> 1
        // ^ The compiler could suggest wrapping this in `Ok`
    "2" -> 2
     _ -> int.parse(value)
  }
}

Rust does this, for example

I think that's a great idea but in that specific case there wouldn't be an error for that clause.

Yes that's true, probably a bad example. Should I open a separate issue for that?

For what, sorry?

My suggestion above

Sorry, I'm a bit confused. There's no type error on that line. How would it work?

In a different case for example:

pub fn wibble() -> Result(Int, Nil) {
  10
//^ here for example
}

Maybe that's not particularly useful though