# \#result

**URL:** https://forums.swift.org/tag/result/704.md

[Latest](https://forums.swift.org/latest.md) · [Categories](https://forums.swift.org/categories.md) · [Tags](https://forums.swift.org/tags.md)

---

## [\[Pitch\] Result success and failure accessors](https://forums.swift.org/t/pitch-result-success-and-failure-accessors/82396)

<div class="topic-metadata">

**Author:** [@corujautx](https://forums.swift.org/u/corujautx)\
**Replies:** 4\
**Last updated:** [October 6, 2025, 9:52am UTC](https://forums.swift.org/t/pitch-result-success-and-failure-accessors/82396 "2025-10-06T09:52:26Z")

</div>

Hi folks! This is a bit inspired by Rust's unwrap\_or / unwrap\_or\_else methods. The idea is having success(or:) / failure(or:)methods in Swift.Result to allow to lift a success or failure without running into throwing …

---

## [Treat Results like Optionals?](https://forums.swift.org/t/treat-results-like-optionals/81456)

<div class="topic-metadata">

**Author:** [@jtint24](https://forums.swift.org/u/jtint24)\
**Replies:** 3\
**Last updated:** [August 3, 2025, 4:32pm UTC](https://forums.swift.org/t/treat-results-like-optionals/81456 "2025-08-03T16:32:23Z")

</div>

Optionals, while not unique to Swift, are of course one of its most core features. But since Swift 5, it's also had a Result\<T,E\> type that in many ways behaves similarly. Both are enums, often indicating a potentially f…

---

## [Should \`Result.map\` and related methods rethrow?](https://forums.swift.org/t/should-result-map-and-related-methods-rethrow/73602)

<div class="topic-metadata">

**Author:** [@ellie20](https://forums.swift.org/u/ellie20)\
**Replies:** 5\
**Last updated:** [August 1, 2024, 9:10am UTC](https://forums.swift.org/t/should-result-map-and-related-methods-rethrow/73602 "2024-08-01T09:10:55Z")

</div>

The equivalent methods on other types, like Array and Optional, rethrow (propagate errors from their closure argument). Given that Result isn't supposed to be used as a replacement for throwing, I don't see a reason for …

---

## [If/guard-let-catch for conveniently accessing both Result type cases](https://forums.swift.org/t/if-guard-let-catch-for-conveniently-accessing-both-result-type-cases/58492)

<div class="topic-metadata">

**Author:** [@Jeehut](https://forums.swift.org/u/Jeehut)\
**Replies:** 42\
**Last updated:** [December 27, 2022, 12:43am UTC](https://forums.swift.org/t/if-guard-let-catch-for-conveniently-accessing-both-result-type-cases/58492 "2022-12-27T00:43:43Z")

</div>

Motivation A few weeks ago, I had asked on Twitter if developers prefer error handling in Swift by using throws vs. returning Result. Of the 102 votes, 45% voted for "I prefer Result", which is 40% more than the 32% who …