kotlin-result
FsToolkit.ErrorHandling
kotlin-result | FsToolkit.ErrorHandling | |
---|---|---|
35 | 10 | |
937 | 446 | |
- | - | |
8.8 | 8.2 | |
12 days ago | 8 days ago | |
Kotlin | F# | |
ISC License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
kotlin-result
-
JEP draft: Exception handling in switch
Author here. I have no idea what you could possibly mean with this comment. The coroutineBinding implementation correctly uses the coroutines API for parallel decomposition of Result bindings, exactly how the Kotlin Corotines guide tells you to (backed by a [Mutex](https://github.com/michaelbull/kotlin-result/blob/master/kot...)). The coroutineBinding isn't even the main selling point of the library, you can use it without using this feature entirely.
Please could you elaborate on what "looking thread safe" means to you? The only portion of the library that supports concurrency *is* thread safe - the unit tests prove it and the use of concurrency primitives such as Kotlin's Mutex are indicative of this. I truly have no idea how you've judged the entirely of the lbirary on whether it's "thread safe" when there is a single function that's related to concurrency and it is very clearly using concurrency primitives.
-
How do you define errors?
Sealed classes in combination with a library like https://github.com/michaelbull/kotlin-result will get you what you need. Essentially at that point you'll be doing error handling the way you would in Rust, where a 1-level deep sealed class containing data classes as children act as the root error type and each of its variants. If you have errors coming from two different domains you just create a wrapper error type for each domain.
-
Result Class with Generic Type for both Success and Failure States
This is a great result lib: https://github.com/michaelbull/kotlin-result
-
Is runCatching in use in any of your projects ? My team is abusing it
Lastly I do not like kotlin's Result and we use the kotlin-result library which is more expressive and not tied to Throwable (similar to Arrow's Either).
-
Struggling with software robustness with Kotlin
In my own code, I started to use explicit error handling. I'm currently experimenting with Result (from https://github.com/michaelbull/kotlin-result) and Raise (from https://arrow-kt.io/).
-
Thoughts on Kotlin Multiplatform?
un-related to multiplatform i've found it extremely helpful to wrap things in a Result type. If something can throw an error, it get's a Result return type. It sounds like that would help your use case too. The built in Result may be useful too
-
Programming with Result
This is a better impl.
- It seems like I'm forced to make this choice at least once a day
-
Are nearly all your functions suspend?
Using a result type can help to differentiate quite nicely. https://github.com/michaelbull/kotlin-result
-
Kotlin Nitpicks: Language and Standard Library
kotlin-result
FsToolkit.ErrorHandling
-
Type setup for effortless error handling with the Result type
Isn't this similar to what https://github.com/demystifyfp/FsToolkit.ErrorHandling does?
-
It seems like I'm forced to make this choice at least once a day
I do think at least some of FSToolkit.ErrorHandling should be part of the core library though, it has nearly everything you could want for using these types.
-
How do I compose the functions with the following signatures?
I'm having trouble following exactly what you're trying to do, but it would probably be easier if you used the builtin Result type in conjunction with FsToolkit.ErrorHandling. The library provides many useful combinators as well as a result, option, and resultOption computation expression.
-
Dealing with workflows in F#
Also shout out to the wonderful FsToolkit.ErrorHandling library, it simplifies working with these so much.
-
F# 6 Hopes and kind of a rant
Monad stacks, most commonly Async>, require a lot of boilerplate to deal with or using something like https://github.com/demystifyfp/FsToolkit.ErrorHandling . Which is fine, but it causes dependency mismatches between libs or type mismatches as everyone is implementing their own. A language solution would be nice...
- FsToolkit.ErrorHandling 2.5.0 Released π
- FsToolkit.ErrorHandling 2.4.0 Released π
- FsToolkit.ErrorHandling 2.3.0 Released π
- FsToolkit.ErrorHandling 2.2.0 π
-
Say hello to "block" - the recently finalized name for the upcoming immutable array type
This library is nice: https://github.com/demystifyfp/FsToolkit.ErrorHandling
What are some alternatives?
result4k
ply - High performance System.Threading.(Value)Task computation expressions for F#
kotlin-monads - Monads for Kotlin
visualfsharp - The Visual F# compiler and tools
Result - The modelling for success/failure of operations in Kotlin and KMM (Kotlin Multiplatform Mobile)
VisualFSharp - The F# compiler, F# core library, F# language service, and F# tooling integration for Visual Studio
Arrow Meta - Functional companion to Kotlin's Compiler
Fable: F# |> BABEL - F# to JavaScript, TypeScript, Python, Rust and Dart Compiler
Komprehensions - Do comprehensions for Kotlin and 3rd party libraries [STABLE]
Optional - A robust option type for C#
Kategory - Ξrrow - Functional companion to Kotlin's Standard Library
fslang-suggestions - The place to make suggestions, discuss and vote on F# language and core library features