mo
go-sumtype
mo | go-sumtype | |
---|---|---|
14 | 11 | |
2,261 | 403 | |
- | - | |
5.9 | 0.0 | |
6 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.
mo
-
Functional Programming Library for Golang by IBM
A simple alternative is the combination of:
- https://github.com/samber/lo
- https://github.com/samber/mo
The split is also nice as you can choose to just use the generic convenience functions from lo without the more FP related things from mo.
-
Handling nil values: Pointers vs Abstractions
Is it a popular approach to use abstractions in general for handling nil values with libraries like null or mo? Should I just stick with pointers? What are your experiences on this topic?
-
samber/lo utility package based on generics
I really like it. Have been using it for a while, just don't overuse it. Also, I recommend github.com/samber/mo
-
Switching from C++ to Rust
Go generics allow all kinds of things https://github.com/samber/mo
-
I know there is no OPTIONALS in go , i hope they implement it , what is the best approach to deal with optionals in go? sometimes i think the default values added by golang isnβt suitable, like adding zero to int ! .. zero is a value not nil or undefined.
Have you taken a look at mo? https://github.com/samber/mo
-
What the state of functional programming ecosystem ?
If you are curious, try looking at github.com/samber/lo and github.com/samber/mo packages if you get a chance.
-
Reduce Boilerplate in Go Http Handlers with Go Generics
I have seen https://github.com/samber/mo but it's a niche. Monads aren't popular in Golang community.
- Monads for Go, Using Generics (Option, Result, Either)
-
Expected vs Unexpected errors in Go
I've also looked at the mo library, in particular to use Option[User] but that's really just a slightly safer way to represent User* here. (Safer because you're forced to check if there's a value and so don't have the same accidental panic risk.)
- Monads and popular FP abstractions, powered by Go 1.18 Generics
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?
lo - π₯ A Lodash-style Go library based on Go 1.18+ Generics (map, filter, contains, find...)
go101 - An up-to-date (unofficial) knowledge base for Go programming self learning
fp-go - fp-go is a collection of Functional Programming helpers powered by Golang 1.18+ generics.
enumer - A Go tool to auto generate methods for your enums
valor - Go option and result types that optionally contain a value
go - The Go programming language
underscore - π Useful functional programming helpers for Go
hylo - The Hylo programming language
gofp - A super simple Lodash like utility library with essential functions that empowers the development in Go
crubit
fuego - Functional Experiment in Golang
go-hasdefault - a go linter to check switch statements for default