go-sumtype
A simple utility for running exhaustiveness checks on Go "sum types." (by BurntSushi)
enumer
A Go tool to auto generate methods for your enums (by dmarkham)
Our great sponsors
go-sumtype | enumer | |
---|---|---|
11 | 6 | |
403 | 369 | |
- | - | |
0.0 | 2.3 | |
about 1 year ago | 2 months ago | |
Go | Go | |
The Unlicense | GNU General Public License v3.0 or later |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
go-sumtype
Posts with mentions or reviews of go-sumtype.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-03-13.
-
Small sum types in Golang
I find this implementation to be quite minimal and less clumsy than alternatives. Sure, you don't get nice exhaustive pattern matching. Also, type inference gets in the way when instantiating UserKey (though you can wrap it in constructor functions). But expressing your intent using types still makes your code much more convenient and easier to understand.
-
Switching from C++ to Rust
The call out to sum types is something I feel. I've been using Rust daily for almost 10 years now, and sum types are absolutely still one of the things I love most about it. It's easily one of the things I miss the most in other languages. I'm usually a proponent of "using languages as they're intended," but I missed exhaustiveness checking so much that I ported a version of it to Go[1] as a sort of lint.
[1]: https://github.com/BurntSushi/go-sumtype
-
Rusty enums in Go
A Google search for golang sum types currently shows my project as a second hit: https://github.com/BurntSushi/go-sumtype
-
Carbon Language: An experimental successor to C++
I've been writing Go and Rust nearly daily for about a decade now (Go is more than a decade, Rust is about 8 years). You are not going to teach me anything about the pros and cons of either language in a reddit comment. I do not need to be taught about the "iota mess" when I've written tooling for exhaustiveness checking in Go.
-
a go linter to check switch statements for default
https://github.com/BurntSushi/go-sumtype forces exhaustive type switches for interfaces specifically annotated to need that.
-
Go: Making state explicit using the type system
We can fix these two problems by relying on static analyzers such as go-sumtypes
-
Hacking sum types with Go generics
See also https://github.com/BurntSushi/go-sumtype
- What I'd like to see in Go 2.0
-
Upcoming Features in Go 1.18
go-sumtype[0] has completeness checking for sealed interfaces.
[0] https://github.com/BurntSushi/go-sumtype
-
I want enum more than generics
Pretty easy to achieve outside of the compiler: https://github.com/BurntSushi/go-sumtype
enumer
Posts with mentions or reviews of enumer.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-03-28.
- Go Enums Still Suck
-
Go isn't the right tool for ANY job
Just use const blocks, iota and enumer and be happy.
-
Does Go not have enums in the sense that I can use them as a type?
Define your type as an alias on int and values using iota as others have said, then autogenerate the rest of the functionality from other languages with https://github.com/dmarkham/enumer
-
Safer Enums in Go
We tried out struct-based enums like this for a while and they're definitely better than the vanilla version, but they still have the problem of "how do you iterate over all the values?" and "how do you create an enum value from a string?". We chanced upon https://github.com/dmarkham/enumer a few months ago and have been very happy so far.
Use enumer in combination with what some of this article.
- What I'd like to see in Go 2.0
What are some alternatives?
When comparing go-sumtype and enumer you can also consider the following projects:
go101 - An up-to-date (unofficial) knowledge base for Go programming self learning
go - The Go programming language
yaegi - Yaegi is Another Elegant Go Interpreter
hylo - The Hylo programming language
go-retry - Go library for retrying with configurable backoffs
crubit
codegena - Codegeneration tool
mo - 🦄 Monads and popular FP abstractions, powered by Go 1.18+ Generics (Option, Result, Either...)
yaegi-template - Use yaegi as a template engine.
go-hasdefault - a go linter to check switch statements for default