rustic_result
ez
rustic_result | ez | |
---|---|---|
5 | 2 | |
21 | 11 | |
- | - | |
5.3 | 2.7 | |
3 months ago | 4 months ago | |
Elixir | Go | |
MIT 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.
rustic_result
-
Switching to Elixir
Self promotion moment:
If you enjoy the Result/Either type and API in Rust, I made this project just for this: https://github.com/linkdd/rustic_result
I also made https://github.com/linkdd/rustic_maybe/tree/main for an Option/Maybe type.
NB: Those are not types, but I'm waiting for set theoretic types to update those libs :)
-
Error Handling Patterns
It's missing the Erlang/Elixir pattern of returning a tuple `{:ok, T}` or `{:error, E}`, where we can then use pattern matching, or `with` expressions, etc...
To be fair, it is very similar to a `Result` type, which is why I made this library a while ago: https://github.com/linkdd/rustic_result
-
A new milestone for Letlang - Effect Handlers
I intend to add a pipeline operator similar to Elixir, to be used with an std::result module which will provide functions to ease writing such complex code. I may take inspiration on an Elixir library I wrote a while ago: https://github.com/linkdd/rustic_result
-
Elixir Railway Oriented Programming
A while ago, I made this library https://github.com/linkdd/rustic_result
-
Go Replaces Interface{} with 'Any'
I also made a library for working with `{:ok, value}` and `{:error, reason}` in Elixir: https://github.com/linkdd/rustic_result
Thanks to the pipeline operator and pattern matching, it makes pretty easy to read pipelines. It does not completely replace the with statement (that was not the point) but it simplified a lot of code.
ez
-
Show HN: Error return traces for Go, inspired by Zig
While from a first instance, this package seems a bit overkill, I think the idea is interesting and is something that can be improved for Go.
I also felt that Go errors where too bare-bones, so I developed a small package (https://github.com/Vanclief/ez) based on an awesome post that I saw here once. I use this package in all Golang code I touch.
-
Go Replaces Interface{} with 'Any'
I used to really hate that. After reading this amazing post https://middlemost.com/failure-is-your-domain I created a module that makes this bearable https://github.com/Vanclief/ez
What are some alternatives?
neverthrow - Type-Safe Errors for JS & TypeScript
errtrace - An alternative to stack traces for your Go errors
eqwalizer - A type-checker for Erlang
errors - Simple error handling primitives
semver - Semantic Versioning Specification
go - The Go programming language
rustic_maybe - Maybe monad for Elixir inspired by Rust Option type
gopherjs - A compiler from Go to JavaScript for running Go code in a browser
transport-site - Rendre disponible, valoriser et améliorer les données transports
js-proposal-algebraic-effects - 📐Let there be algebraic effects in JS
gen_stage - Producer and consumer actors with back-pressure for Elixir
mux - A powerful HTTP router and URL matcher for building Go web servers with 🦍