# SE-0244: Opaque Result Types **URL:** \ **Category:** Proposal Reviews\ **Created:** [March 5, 2019, 9:40pm UTC](https://forums.swift.org/t/se-0244-opaque-result-types/21252 "2019-03-05T21:40:52Z")\ **Posts on this page:** 1\ **Showing post:** 89
**Author:** ![orobio](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/orobio/32/5512_2.png) [@orobio](https://forums.swift.org/u/orobio)\ **Post date:** [March 14, 2019, 1:04pm UTC](https://forums.swift.org/t/se-0244-opaque-result-types/21252/89 "2019-03-14T13:04:14Z")
For people that are still confused about opaque result types, I did an attempt to explain them from the perspective of the earlier mentioned 'reverse generics'. It would also be helpful if some people with more knowledge could have a look at it and point out any errors. > [@Reverse generics and opaque result types](https://forums.swift.org/t/reverse-generics-and-opaque-result-types/21608): > > Introduction I've been trying to wrap my head around [SE-0244: Opaque Result Types](https://forums.swift.org/t/se-0244-opaque-result-types/21252) and recently I had some realizations that helped me understand the proposal better. I noticed I'm not the only one confused about it, so I thought I'd write down some things that might help others to get a better grasp of the concept as well. In doing so, I'd also like to try and rebrand opaque result types, or at least the underlying mechanism, to something I'm calling 'reverse generics'. I think viewing this al… --- _[View the full topic](https://forums.swift.org/t/se-0244-opaque-result-types/21252)._