Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / michaelbull/kotlin-result issues and pull requests
#50 - Move coroutine tests to use kotlinx-coroutines-test instead of runBlockingTest
Issue -
State: closed - Opened by Munzey over 3 years ago
- 3 comments
#50 - Move coroutine tests to use kotlinx-coroutines-test instead of runBlockingTest
Issue -
State: closed - Opened by Munzey over 3 years ago
- 3 comments
#49 - Set JS compiler to BOTH
Pull Request -
State: closed - Opened by gsteckman over 3 years ago
- 1 comment
#49 - Set JS compiler to BOTH
Pull Request -
State: closed - Opened by gsteckman over 3 years ago
- 1 comment
#49 - Set JS compiler to BOTH
Pull Request -
State: closed - Opened by gsteckman over 3 years ago
- 1 comment
#49 - Set JS compiler to BOTH
Pull Request -
State: closed - Opened by gsteckman over 3 years ago
- 1 comment
#49 - Set JS compiler to BOTH
Pull Request -
State: closed - Opened by gsteckman over 3 years ago
- 1 comment
#48 - Added Linux, Windows and MacOS targets
Pull Request -
State: closed - Opened by avently over 3 years ago
- 9 comments
#48 - Added Linux, Windows and MacOS targets
Pull Request -
State: closed - Opened by avently over 3 years ago
- 9 comments
#48 - Added Linux, Windows and MacOS targets
Pull Request -
State: closed - Opened by avently over 3 years ago
- 9 comments
#48 - Added Linux, Windows and MacOS targets
Pull Request -
State: closed - Opened by avently over 3 years ago
- 9 comments
#47 - Move benchmarks to separate module
Pull Request -
State: closed - Opened by Munzey over 3 years ago
- 2 comments
#47 - Move benchmarks to separate module
Pull Request -
State: closed - Opened by Munzey over 3 years ago
- 2 comments
#47 - Move benchmarks to separate module
Pull Request -
State: closed - Opened by Munzey over 3 years ago
- 2 comments
#47 - Move benchmarks to separate module
Pull Request -
State: closed - Opened by Munzey over 3 years ago
- 2 comments
#47 - Move benchmarks to separate module
Pull Request -
State: closed - Opened by Munzey over 3 years ago
- 2 comments
#47 - Move benchmarks to separate module
Pull Request -
State: closed - Opened by Munzey over 3 years ago
- 2 comments
#47 - Move benchmarks to separate module
Pull Request -
State: closed - Opened by Munzey over 3 years ago
- 2 comments
#47 - Move benchmarks to separate module
Pull Request -
State: closed - Opened by Munzey over 3 years ago
- 2 comments
#47 - Move benchmarks to separate module
Pull Request -
State: closed - Opened by Munzey over 3 years ago
- 2 comments
#47 - Move benchmarks to separate module
Pull Request -
State: closed - Opened by Munzey over 3 years ago
- 2 comments
#47 - Move benchmarks to separate module
Pull Request -
State: closed - Opened by Munzey over 3 years ago
- 2 comments
#47 - Move benchmarks to separate module
Pull Request -
State: closed - Opened by Munzey over 3 years ago
- 2 comments
#47 - Move benchmarks to separate module
Pull Request -
State: closed - Opened by Munzey over 3 years ago
- 2 comments
#47 - Move benchmarks to separate module
Pull Request -
State: closed - Opened by Munzey over 3 years ago
- 2 comments
#47 - Move benchmarks to separate module
Pull Request -
State: closed - Opened by Munzey over 3 years ago
- 2 comments
#47 - Move benchmarks to separate module
Pull Request -
State: closed - Opened by Munzey over 3 years ago
- 2 comments
#46 - Clean up suspend binding implementation
Pull Request -
State: closed - Opened by Munzey over 3 years ago
- 25 comments
#46 - Clean up suspend binding implementation
Pull Request -
State: closed - Opened by Munzey over 3 years ago
- 25 comments
#45 - Next release?
Issue -
State: closed - Opened by breucode over 3 years ago
- 2 comments
#45 - Next release?
Issue -
State: closed - Opened by breucode over 3 years ago
- 2 comments
#45 - Next release?
Issue -
State: closed - Opened by breucode over 3 years ago
- 2 comments
#45 - Next release?
Issue -
State: closed - Opened by breucode over 3 years ago
- 2 comments
#45 - Next release?
Issue -
State: closed - Opened by breucode over 3 years ago
- 2 comments
#45 - Next release?
Issue -
State: closed - Opened by breucode over 3 years ago
- 2 comments
#45 - Next release?
Issue -
State: closed - Opened by breucode over 3 years ago
- 2 comments
#45 - Next release?
Issue -
State: closed - Opened by breucode over 3 years ago
- 2 comments
#44 - Typo in wiki for checking if result is an error
Issue -
State: closed - Opened by stigkj over 3 years ago
- 1 comment
#44 - Typo in wiki for checking if result is an error
Issue -
State: closed - Opened by stigkj over 3 years ago
- 1 comment
#44 - Typo in wiki for checking if result is an error
Issue -
State: closed - Opened by stigkj over 3 years ago
- 1 comment
#44 - Typo in wiki for checking if result is an error
Issue -
State: closed - Opened by stigkj over 3 years ago
- 1 comment
#44 - Typo in wiki for checking if result is an error
Issue -
State: closed - Opened by stigkj over 3 years ago
- 1 comment
#44 - Typo in wiki for checking if result is an error
Issue -
State: closed - Opened by stigkj over 3 years ago
- 1 comment
#43 - Are there plans for a website for documenting functionality?
Issue -
State: closed - Opened by shalomhalbert almost 4 years ago
- 8 comments
#43 - Are there plans for a website for documenting functionality?
Issue -
State: closed - Opened by shalomhalbert almost 4 years ago
- 8 comments
#43 - Are there plans for a website for documenting functionality?
Issue -
State: closed - Opened by shalomhalbert almost 4 years ago
- 8 comments
#43 - Are there plans for a website for documenting functionality?
Issue -
State: closed - Opened by shalomhalbert almost 4 years ago
- 8 comments
#43 - Are there plans for a website for documenting functionality?
Issue -
State: closed - Opened by shalomhalbert almost 4 years ago
- 8 comments
#43 - Are there plans for a website for documenting functionality?
Issue -
State: closed - Opened by shalomhalbert almost 4 years ago
- 8 comments
#43 - Are there plans for a website for documenting functionality?
Issue -
State: closed - Opened by shalomhalbert almost 4 years ago
- 8 comments
#43 - Are there plans for a website for documenting functionality?
Issue -
State: closed - Opened by shalomhalbert almost 4 years ago
- 8 comments
#43 - Are there plans for a website for documenting functionality?
Issue -
State: closed - Opened by shalomhalbert almost 4 years ago
- 8 comments
#43 - Are there plans for a website for documenting functionality?
Issue -
State: closed - Opened by shalomhalbert almost 4 years ago
- 8 comments
#43 - Are there plans for a website for documenting functionality?
Issue -
State: closed - Opened by shalomhalbert almost 4 years ago
- 8 comments
#43 - Are there plans for a website for documenting functionality?
Issue -
State: closed - Opened by shalomhalbert almost 4 years ago
- 8 comments
#42 - Should we offer a binding that can bind results of any Error type?
Issue -
State: closed - Opened by Munzey almost 4 years ago
- 1 comment
#42 - Should we offer a binding that can bind results of any Error type?
Issue -
State: closed - Opened by Munzey almost 4 years ago
- 1 comment
#42 - Should we offer a binding that can bind results of any Error type?
Issue -
State: closed - Opened by Munzey almost 4 years ago
- 1 comment
#42 - Should we offer a binding that can bind results of any Error type?
Issue -
State: closed - Opened by Munzey almost 4 years ago
- 1 comment
#42 - Should we offer a binding that can bind results of any Error type?
Issue -
State: closed - Opened by Munzey almost 4 years ago
- 1 comment
#42 - Should we offer a binding that can bind results of any Error type?
Issue -
State: closed - Opened by Munzey almost 4 years ago
- 1 comment
#42 - Should we offer a binding that can bind results of any Error type?
Issue -
State: closed - Opened by Munzey almost 4 years ago
- 1 comment
#42 - Should we offer a binding that can bind results of any Error type?
Issue -
State: closed - Opened by Munzey almost 4 years ago
- 1 comment
#42 - Should we offer a binding that can bind results of any Error type?
Issue -
State: closed - Opened by Munzey almost 4 years ago
- 1 comment
#42 - Should we offer a binding that can bind results of any Error type?
Issue -
State: closed - Opened by Munzey almost 4 years ago
- 1 comment
#42 - Should we offer a binding that can bind results of any Error type?
Issue -
State: closed - Opened by Munzey almost 4 years ago
- 1 comment
#42 - Should we offer a binding that can bind results of any Error type?
Issue -
State: closed - Opened by Munzey almost 4 years ago
- 1 comment
#42 - Should we offer a binding that can bind results of any Error type?
Issue -
State: closed - Opened by Munzey almost 4 years ago
- 1 comment
#42 - Should we offer a binding that can bind results of any Error type?
Issue -
State: closed - Opened by Munzey almost 4 years ago
- 1 comment
#41 - Move benchmarks to separate module
Pull Request -
State: closed - Opened by hanleyt almost 4 years ago
- 4 comments
#41 - Move benchmarks to separate module
Pull Request -
State: closed - Opened by hanleyt almost 4 years ago
- 4 comments
#41 - Move benchmarks to separate module
Pull Request -
State: closed - Opened by hanleyt almost 4 years ago
- 4 comments
#41 - Move benchmarks to separate module
Pull Request -
State: closed - Opened by hanleyt almost 4 years ago
- 4 comments
#41 - Move benchmarks to separate module
Pull Request -
State: closed - Opened by hanleyt almost 4 years ago
- 4 comments
#41 - Move benchmarks to separate module
Pull Request -
State: closed - Opened by hanleyt almost 4 years ago
- 4 comments
#41 - Move benchmarks to separate module
Pull Request -
State: closed - Opened by hanleyt almost 4 years ago
- 4 comments
#41 - Move benchmarks to separate module
Pull Request -
State: closed - Opened by hanleyt almost 4 years ago
- 4 comments
#41 - Move benchmarks to separate module
Pull Request -
State: closed - Opened by hanleyt almost 4 years ago
- 4 comments
#41 - Move benchmarks to separate module
Pull Request -
State: closed - Opened by hanleyt almost 4 years ago
- 4 comments
#41 - Move benchmarks to separate module
Pull Request -
State: closed - Opened by hanleyt almost 4 years ago
- 4 comments
#41 - Move benchmarks to separate module
Pull Request -
State: closed - Opened by hanleyt almost 4 years ago
- 4 comments
#41 - Move benchmarks to separate module
Pull Request -
State: closed - Opened by hanleyt almost 4 years ago
- 4 comments
#40 - Add recoverIf and recoverUnless
Pull Request -
State: closed - Opened by oddsund almost 4 years ago
#40 - Add recoverIf and recoverUnless
Pull Request -
State: closed - Opened by oddsund almost 4 years ago
#40 - Add recoverIf and recoverUnless
Pull Request -
State: closed - Opened by oddsund almost 4 years ago
#40 - Add recoverIf and recoverUnless
Pull Request -
State: closed - Opened by oddsund almost 4 years ago
#40 - Add recoverIf and recoverUnless
Pull Request -
State: closed - Opened by oddsund almost 4 years ago
#40 - Add recoverIf and recoverUnless
Pull Request -
State: closed - Opened by oddsund almost 4 years ago
#40 - Add recoverIf and recoverUnless
Pull Request -
State: closed - Opened by oddsund almost 4 years ago
#40 - Add recoverIf and recoverUnless
Pull Request -
State: closed - Opened by oddsund almost 4 years ago
#40 - Add recoverIf and recoverUnless
Pull Request -
State: closed - Opened by oddsund almost 4 years ago
#40 - Add recoverIf and recoverUnless
Pull Request -
State: closed - Opened by oddsund almost 4 years ago
#39 - Mapping a failure to success given a predicate
Issue -
State: closed - Opened by oddsund almost 4 years ago
- 1 comment
#39 - Mapping a failure to success given a predicate
Issue -
State: closed - Opened by oddsund almost 4 years ago
- 1 comment
#39 - Mapping a failure to success given a predicate
Issue -
State: closed - Opened by oddsund almost 4 years ago
- 1 comment
#39 - Mapping a failure to success given a predicate
Issue -
State: closed - Opened by oddsund almost 4 years ago
- 1 comment
#39 - Mapping a failure to success given a predicate
Issue -
State: closed - Opened by oddsund almost 4 years ago
- 1 comment
#39 - Mapping a failure to success given a predicate
Issue -
State: closed - Opened by oddsund almost 4 years ago
- 1 comment
#39 - Mapping a failure to success given a predicate
Issue -
State: closed - Opened by oddsund almost 4 years ago
- 1 comment
#39 - Mapping a failure to success given a predicate
Issue -
State: closed - Opened by oddsund almost 4 years ago
- 1 comment