sqlread
go-sumtype
| sqlread | go-sumtype | |
|---|---|---|
| 1 | 11 | |
| 48 | 403 | |
| - | - | |
| 5.5 | 0.0 | |
| 4 months ago | about 1 year ago | |
| Go | Go | |
| MIT License | The Unlicense |
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.
sqlread
-
What I'd like to see in Go 2.0
> Use int-type enums with iota: no human-readable error values, no compile-time guard against illegal enum values
Create a new int type and use that for your enums. You have to try really hard to get a bad value in that case, and if it’s an unpunished type in a different package it’s even harder.
See:
https://github.com/donatj/sqlread/blob/91b4f07370d12d697d18a...
go-sumtype
-
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
What are some alternatives?
go-retry - Go library for retrying with configurable backoffs
go101 - An up-to-date (unofficial) knowledge base for Go programming self learning
enumer - A Go tool to auto generate methods for your enums
swift-evolution - This maintains proposals for changes and user-visible enhancements to the Swift Programming Language.
go - The Go programming language
hylo - The Hylo programming language
yaegi - Yaegi is Another Elegant Go Interpreter
crubit
mo - 🦄 Monads and popular FP abstractions, powered by Go 1.18+ Generics (Option, Result, Either...)