Exhaustive Alternatives

exhaustive reviews and mentions

• Enums in Go
  6 projects | news.ycombinator.com | 12 Jul 2024

  There are two linters that add those checks: https://github.com/nishanths/exhaustive for values and https://github.com/alecthomas/go-check-sumtype for types. Both are integrated into golangci-lint. I use both a lot and have only a positive experience.

  Having support from the language would be nice, though.

• Compile-time safety for enumerations in Go
  3 projects | news.ycombinator.com | 29 Sep 2023

  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
  36 projects | /r/golang | 26 Mar 2023

  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?
  17 projects | /r/golang | 10 Mar 2023

  there’s a linter for exhaustive matching: https://github.com/nishanths/exhaustive

• Rusty enums in Go
  5 projects | /r/golang | 16 Feb 2023

  I tried to find that linter and found this: exhaustive

• Supporting the Use of Rust in the Chromium Project
  11 projects | /r/rust | 13 Jan 2023

  And in Go you'd use a linter, like this one.

• Blog on enums in Go: benchmarks; issues; assembly
  2 projects | /r/golang | 16 Nov 2022

  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
  15 projects | news.ycombinator.com | 2 Jun 2022

  >> 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?
  5 projects | /r/golang | 22 May 2022

  Use a linter.

• 1.18 is released
  6 projects | /r/golang | 15 Mar 2022

  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?

• A note from our sponsor - CodeRabbit
  coderabbit.ai | 30 Apr 2025

  Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR. Learn more →