exhaustive
lo
Our great sponsors
exhaustive | lo | |
---|---|---|
11 | 64 | |
268 | 15,293 | |
- | - | |
6.2 | 6.1 | |
10 days ago | 1 day ago | |
Go | Go | |
BSD 2-clause "Simplified" 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.
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.
lo
-
Go 1.22 Release Notes
On the other hand, I advise you NOT to use this kind of library and write simple, fast go code most of the time, with the occasional generics helper. Why the hell would I clutter my code with, for example: https://github.com/samber/lo?tab=readme-ov-file#fromentries-...
-
Go is not an easy language (2021)
This wasn't feasable without generics, and now with generics they're already adding some convenience functions to the stdlib, like in the slices package.
For map, reduce etc it's not in the stdlib yet, but you can use https://pkg.go.dev/github.com/samber/lo
- I wrote a for loop so you don't have to. Parallel Map, Filter, Reduce library
-
What is your recommendation for a package beyond std?
In particular, I'd like recommend samber/lo, this is a lodash generic tool for golang.
-
What 3rd-party libraries do you use often/all the time?
What are some 3rd-party libraries for Go that you use often/all the time? Instead of "just implement everything yourself", I would really like to get some tips. For instance, a few days ago I discovered https://github.com/samber/lo , which looks very good if I want to have list comprehensions (Python) / LINQ methods (C#). https://pkg.go.dev/github.com/atotto/clipboard is also good for clipboard operations. What else do you suggest and for what task?
- Fourteen Years of Go
-
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.
- Khan Academy's switch from a Python 2 monolith to a services-oriented backend written in Go.
-
In what ways are channels are better than the traditional await?
Some packages offer utilities to gather results from goroutines, such as multierror.Group or parallel.Map in samber/lo.
-
samber/lo utility package based on generics
I came across samber/log a package based on generics for providing utility methods.
What are some alternatives?
golangci-lint - Fast linters Runner for Go
underscore - 🌟 Useful functional programming helpers for Go
reposurgeon
mo - 🦄 Monads and popular FP abstractions, powered by Go 1.18+ Generics (Option, Result, Either...)
Ionide-vim - F# Vim plugin based on FsAutoComplete and LSP protocol
go-godash - An experimental generic functional utility library inspired by Lodash
go-optional - A library that provides Go Generics friendly "optional" features.
fpGo - Monad, Functional Programming features for Golang
enumcheck - Allows to mark Go enum types as exhaustive.
fp-go - fp-go is a collection of Functional Programming helpers powered by Golang 1.18+ generics.
server
go-generic-optional - Implementation of Optionals in Go using Generics