rustic_result
exhaustive
rustic_result | exhaustive | |
---|---|---|
5 | 11 | |
21 | 276 | |
- | - | |
5.3 | 5.9 | |
3 months ago | 12 days ago | |
Elixir | Go | |
MIT License | BSD 2-clause "Simplified" 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.
exhaustive
-
Compile-time safety for enumerations in Go
This is an analyzer that will catch this: https://github.com/nishanths/exhaustive
I believe it's in golangci-lint.
-
Tools besides Go for a newbie
I agree linters in general are quite useful for Go though. The default suite from golangci-lint is quite good. I would also recommend enabling exhaustive if you're working with a codebase that uses "enums" (full disclosure, I contributed a bit to that project).
-
What “sucks” about Golang?
there’s a linter for exhaustive matching: https://github.com/nishanths/exhaustive
-
Rusty enums in Go
I tried to find that linter and found this: exhaustive
-
Supporting the Use of Rust in the Chromium Project
And in Go you'd use a linter, like this one.
-
Blog on enums in Go: benchmarks; issues; assembly
this is AST go vet analyzer that performs just that: https://github.com/nishanths/exhaustive (too bad it can not do struct based enums..)
-
Rust Is Hard, Or: The Misery of Mainstream Programming
>> the main thing missing from Go is ADT's. After using these in Rust and Swift, a programming language doesn't really feel complete without them
What are the differences between an ADT (plus pattern matching i’d reckon?) in Rust/Swift vs the equiv in Go (tagged interfaces + switch statement)?
One has exhaustive matching at compile time, the other has a default clause (non exhaustive matching), although there’s an important nub here with respect to developer experience; it would be idiomatic in Go to use static analysis tooling (e.g. Rob Pike is on record saying that various checks - inc this one - don’t belong in the compiler and should live in go vet). I’ve been playing with Go in a side project and using golint-ci which invokes https://github.com/nishanths/exhaustive - net result, in both go and rust, i get a red line of text annotated at the switch in vscode if i miss a case.
Taking a step back, there isn’t a problem you can solve with one that you can’t solve with the other, or is there?
To take a step further back, why incomplete?
-
Why are enums not a thing in Go?
Use a linter.
-
1.18 is released
For an exhaustive linter, were you referring to this? It looks pretty nice. If it's possible to check this with static analysis, is it something that could be in the compiler itself in the future?
-
Go Replaces Interface{} with 'Any'
https://github.com/nishanths/exhaustive
here, have fun. You’re gonna write some tests, make new types to satisfy interfaces for testing, and then wind up with branches for your test paths in your live code, but go for it, I guess. You know everything! I am but a simple blubbite, too dim, too dim to get it.
What are some alternatives?
neverthrow - Type-Safe Errors for JS & TypeScript
golangci-lint - Fast linters runner for Go
eqwalizer - A type-checker for Erlang
reposurgeon
semver - Semantic Versioning Specification
Ionide-vim - F# Vim plugin based on FsAutoComplete and LSP protocol
go - The Go programming language
go-optional - A library that provides Go Generics friendly "optional" features.
rustic_maybe - Maybe monad for Elixir inspired by Rust Option type
ionide-vscode-fsharp - VS Code plugin for F# development
gopherjs - A compiler from Go to JavaScript for running Go code in a browser
enumcheck - Allows to mark Go enum types as exhaustive.