[Bikeshedding]: Supporting throwing transforms on Result

[gwendal.roue (Gwendal Roué)]

I don't understand. Nobody has any problem with applying multiple throwing transformations. The problem lies in the frontier between Result-based apis, and regular throwing methods (which are the idiomatic way to transform values with eventual error). It is very simple, and has been well explained: there is no point stating it again.

A flatMap with a throwing closure has been requested during the pitch, the review, and regrets have been expressed after SE-0235 had shipped without it. The rationale did not close the door:

@John_McCall

Several members of the community voiced disappointment that the proposal did not include a variant of flatMap that took a throwing closure. The Core Team reaffirms its desire to never overload methods by whether an argument function can throw. We spent quite some time debating whether a different name would be acceptable, such as flatMapThrowing , but were unable to reach consensus on this, especially as there are alternative means of expressing this using the catching initializer.

Edit: it's just a discussion about a convenience API, nothing more... There is no "big problem in Swift"...