michaelbull/kotlin-result issues and pull requests

#110 - Kotlin doesn't support exporting inline classes to Objective-C/Swift, making Result 2.x a no-go for APIs consumed in iOS

Issue - State: open - Opened by tiwoc about 1 month ago
Labels: question, discussion

#109 - Using Result<V, E> in Swift for a KMP Project

Issue - State: open - Opened by sayah-y about 2 months ago - 4 comments
Labels: question

#108 - Question: Creating an instance of Result<V, E> in Swift

Issue - State: closed - Opened by curioustechizen about 2 months ago - 3 comments

#107 - Update link monad_comprehensions Arrow (Kotlin) README.md

Pull Request - State: open - Opened by hoangchungk53qx1 2 months ago

#106 - Fixing Indeterminate Behavior Caused by `InvocationKind.EXACTLY_ONCE`

Pull Request - State: open - Opened by Daiji256 3 months ago - 6 comments

#105 - Provide `mapIfInstance`?

Issue - State: open - Opened by nikclayton 4 months ago - 1 comment
Labels: enhancement, discussion

#104 - Result 2.0: unsafe unwrapping of `Result.value` and `Result.error`

Issue - State: open - Opened by kirillzh 4 months ago - 3 comments
Labels: discussion

#103 - Detekt rule to detect missing `.bind()` calls inside `suspendBinding` and `binding`

Issue - State: open - Opened by kirillzh 5 months ago - 3 comments
Labels: enhancement, help wanted, good first issue

#102 - Issues with @JvmStatic code

Issue - State: closed - Opened by Takiguchi72 6 months ago - 4 comments

#101 - How to use the new inlined Result in non-Kotlin code?

Issue - State: closed - Opened by efenderbosch-atg 7 months ago - 9 comments

#100 - Kotlin bugs with value classes

Issue - State: closed - Opened by nikclayton 7 months ago - 4 comments

#99 - v2

Pull Request - State: closed - Opened by michaelbull 7 months ago

#98 - Use List as return type for zipOrAccumulate

Pull Request - State: closed - Opened by YuitoSato 7 months ago - 2 comments

#97 - Use List as return type for zipOrAccumulate

Pull Request - State: closed - Opened by YuitoSato 7 months ago - 1 comment

#96 - Make BindException public

Issue - State: closed - Opened by CharlieTap 7 months ago - 5 comments

#95 - `orElse` for Error Type Transformation

Issue - State: closed - Opened by Hosshii 7 months ago - 2 comments

#94 - Add tryRecoverIf and tryRecoverUnless functions

Pull Request - State: closed - Opened by Jhabkin 9 months ago - 8 comments

#93 - Discuss: Use coroutines instead of exceptions for binding

Issue - State: open - Opened by dronda-t 11 months ago - 2 comments
Labels: discussion

#92 - Document the order of output lists in Iterable.kt

Pull Request - State: closed - Opened by peter-cunderlik-kmed 12 months ago

#91 - Documentation of order of elements in Iterable.kt

Issue - State: closed - Opened by peter-cunderlik-kmed 12 months ago - 2 comments

#90 - add zipOrAccumulate

Pull Request - State: closed - Opened by YuitoSato about 1 year ago

#89 - Consider adding zipOrAccumulate?

Issue - State: closed - Opened by YuitoSato about 1 year ago - 13 comments

#88 - Consider using consistent "error" naming over "failure"?

Issue - State: closed - Opened by kirillzh about 1 year ago - 2 comments

#87 - Recovery extension

Issue - State: closed - Opened by caiofaustino over 1 year ago - 3 comments

#86 - toErrorIfNull to return Result with non-null value.

Pull Request - State: closed - Opened by kirillzh over 1 year ago - 2 comments

#85 - e: Could not load module <Error module>

Issue - State: closed - Opened by argenkiwi over 1 year ago - 6 comments

#85 - e: Could not load module <Error module>

Issue - State: closed - Opened by argenkiwi over 1 year ago - 4 comments

#85 - e: Could not load module <Error module>

Issue - State: closed - Opened by argenkiwi over 1 year ago - 6 comments

#84 - ensureNotNull-alike binding scope extensions

Issue - State: closed - Opened by kirillzh over 1 year ago - 15 comments

#83 - Add VersionCatalogs

Pull Request - State: closed - Opened by bitPogo over 1 year ago - 3 comments

#83 - Add VersionCatalogs

Pull Request - State: closed - Opened by bitPogo over 1 year ago - 3 comments

#83 - Add VersionCatalogs

Pull Request - State: closed - Opened by bitPogo over 1 year ago - 3 comments

#82 - Use `api` in lieu of `implementation`

Pull Request - State: closed - Opened by 05nelsonm over 1 year ago

#82 - Use `api` in lieu of `implementation`

Pull Request - State: closed - Opened by 05nelsonm over 1 year ago

#82 - Use `api` in lieu of `implementation`

Pull Request - State: closed - Opened by 05nelsonm over 1 year ago

#81 - Add support for additional multiplatform targets

Pull Request - State: closed - Opened by 05nelsonm over 1 year ago - 10 comments

#81 - Add support for additional multiplatform targets

Pull Request - State: closed - Opened by 05nelsonm over 1 year ago - 10 comments

#81 - Add support for additional multiplatform targets

Pull Request - State: closed - Opened by 05nelsonm over 1 year ago - 10 comments

#81 - Add support for additional multiplatform targets

Pull Request - State: closed - Opened by 05nelsonm over 1 year ago - 10 comments

#80 - Best practices for integrating with Flow<T>

Issue - State: closed - Opened by Gregory991 almost 2 years ago - 1 comment

#80 - Best practices for integrating with Flow<T>

Issue - State: closed - Opened by Gregory991 almost 2 years ago - 1 comment

#80 - Best practices for integrating with Flow<T>

Issue - State: closed - Opened by Gregory991 almost 2 years ago - 1 comment

#80 - Best practices for integrating with Flow<T>

Issue - State: closed - Opened by Gregory991 almost 2 years ago - 1 comment

#80 - Best practices for integrating with Flow<T>

Issue - State: closed - Opened by Gregory991 almost 2 years ago - 1 comment

#80 - Best practices for integrating with Flow<T>

Issue - State: closed - Opened by Gregory991 almost 2 years ago - 1 comment

#80 - Best practices for integrating with Flow<T>

Issue - State: closed - Opened by Gregory991 almost 2 years ago - 1 comment

#80 - Best practices for integrating with Flow<T>

Issue - State: closed - Opened by Gregory991 almost 2 years ago - 1 comment

#80 - Best practices for integrating with Flow<T>

Issue - State: closed - Opened by Gregory991 almost 2 years ago - 1 comment

#79 - About component1() and 2

Issue - State: closed - Opened by caiofaustino about 2 years ago - 2 comments

#79 - About component1() and 2

Issue - State: closed - Opened by caiofaustino about 2 years ago - 2 comments

#79 - About component1() and 2

Issue - State: closed - Opened by caiofaustino about 2 years ago - 2 comments

#79 - About component1() and 2

Issue - State: closed - Opened by caiofaustino about 2 years ago - 2 comments

#79 - About component1() and 2

Issue - State: closed - Opened by caiofaustino about 2 years ago - 2 comments

#79 - About component1() and 2

Issue - State: closed - Opened by caiofaustino about 2 years ago - 2 comments

#79 - About component1() and 2

Issue - State: closed - Opened by caiofaustino about 2 years ago - 2 comments

#78 - Extensions for Kotlin Flow?

Issue - State: open - Opened by curioustechizen about 2 years ago - 7 comments

#78 - Extensions for Kotlin Flow?

Issue - State: open - Opened by curioustechizen about 2 years ago - 7 comments

#78 - Extensions for Kotlin Flow?

Issue - State: open - Opened by curioustechizen about 2 years ago - 7 comments

#78 - Extensions for Kotlin Flow?

Issue - State: open - Opened by curioustechizen about 2 years ago - 7 comments

#78 - Extensions for Kotlin Flow?

Issue - State: open - Opened by curioustechizen about 2 years ago - 7 comments

#78 - Extensions for Kotlin Flow?

Issue - State: open - Opened by curioustechizen about 2 years ago - 7 comments
Labels: discussion

#78 - Extensions for Kotlin Flow?

Issue - State: open - Opened by curioustechizen about 2 years ago - 7 comments

#78 - Extensions for Kotlin Flow?

Issue - State: open - Opened by curioustechizen about 2 years ago - 7 comments

#78 - Extensions for Kotlin Flow?

Issue - State: open - Opened by curioustechizen about 2 years ago - 7 comments

#78 - Extensions for Kotlin Flow?

Issue - State: open - Opened by curioustechizen about 2 years ago - 7 comments

#77 - Feature request: mingwX86 target

Issue - State: closed - Opened by JohnLCaron about 2 years ago - 2 comments

#77 - Feature request: mingwX86 target

Issue - State: closed - Opened by JohnLCaron about 2 years ago - 2 comments

#77 - Feature request: mingwX86 target

Issue - State: closed - Opened by JohnLCaron about 2 years ago - 2 comments

#77 - Feature request: mingwX86 target

Issue - State: closed - Opened by JohnLCaron about 2 years ago - 2 comments

#77 - Feature request: mingwX86 target

Issue - State: closed - Opened by JohnLCaron about 2 years ago - 2 comments

#77 - Feature request: mingwX86 target

Issue - State: closed - Opened by JohnLCaron about 2 years ago - 2 comments