# \[Accepted with Modifications\] SE-0328: Structural opaque result type **URL:** \ **Category:** Announcements\ **Created:** [November 30, 2021, 6:32pm UTC](https://forums.swift.org/t/accepted-with-modifications-se-0328-structural-opaque-result-type/53789 "2021-11-30T18:32:25Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![ben-cohen](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/ben-cohen/32/296_2.png) [@ben-cohen](https://forums.swift.org/u/ben-cohen)\ **Post date:** [November 30, 2021, 6:32pm UTC](https://forums.swift.org/t/accepted-with-modifications-se-0328-structural-opaque-result-type/53789/1 "2021-11-30T18:32:25Z")
Hello Swift Community, The [review](https://forums.swift.org/t/se-0328-structural-opaque-result-types/53248) of [SE-0328: Structural opaque result types](https://github.com/apple/swift-evolution/blob/main/proposals/0328-structural-opaque-result-types.md) has completed. Feedback was positive, and the core team has **accepted** this proposal **with modification**. During the review there were two main areas of discussion: - The spelling of optional types. The proposal leaves this as `(some P)?` even though `some P?` is more succinct and could potentially be allowed as sugar. The core team agrees with this more conservative approach, which could be revisited later after more experience with the feature. - The use of `some` in "consuming" rather than "producing" position when returning function types i.e. `f() -> (some P) -> Void`. Discussion of other uses of the `some` keyword is ongoing, and there was concern about potential conflict with those future uses. Since the use of opaque result types in consuming position is not especially useful (such functions are uncallable in all but a few circumstances) the core team has decided to subset out this use, requiring opaque result types only in the return value of returned function types for now. Thank you to everyone who participated in the review! Ben Cohen Review Manager