SE-0244: Opaque Result Types

You've figured out the main problem with this proposal: It's not very powerful, so you know that you as the app developer won't need it, but merely consume these types from frameworks that you're using, including the standard library, however, frameworks can't actually use it, because it would mess up the composability of their function return values, as my code above shows.

So, no one can use this productively.