Check exhaustiveness of switch statements of enum-like constants in Go source code. (by nishanths)

Exhaustive Alternatives

Similar projects and alternatives to exhaustive

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better exhaustive alternative or higher similarity.

exhaustive reviews and mentions

Posts with mentions or reviews of exhaustive. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-09-29.
  • 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?
  • Go Replaces Interface{} with 'Any'
    10 projects | news.ycombinator.com | 14 Dec 2021

    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.

  • A note from our sponsor - SaaSHub
    www.saashub.com | 18 May 2024
    SaaSHub helps you find the best software and product alternatives Learn more →


Basic exhaustive repo stats
14 days ago

SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives