# 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:** 5
**Author:** ![beccadax](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/beccadax/32/34217_2.png) [@beccadax](https://forums.swift.org/u/beccadax)\ **Post date:** [March 6, 2019, 12:05am UTC](https://forums.swift.org/t/se-0244-opaque-result-types/21252/5 "2019-03-06T00:05:50Z")
I'm in favor of the feature and I think the proposal covers enough ground to be a useful addition to the language. However, the vague syntax suggestions in the "Future Directions" section concern me. I'm worried that the `-> some P` syntax may be adequate for this proposal's purposes, but may not extend cleanly to uses we envision in the future. Maybe there is some larger scheme we could fit the `some` syntax into; if so, I'd like to see a sketch of that scheme before we commit to it here. (More thoughts on that [in the `Protocol<.AssocType == T>` thread](https://forums.swift.org/t/protocol-assoctype-t-shorthand-for-combined-protocol-and-associated-type-constraints-without-naming-the-constrained-type/21217/10).) Otherwise, I support it. --- _[View the full topic](https://forums.swift.org/t/se-0244-opaque-result-types/21252)._