exhaustive VS errors

Compare exhaustive vs errors and see what are their differences.

exhaustive

Check exhaustiveness of switch statements of enum-like constants. (by nishanths)

errors

Simple error handling primitives (by pkg)
Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
exhaustive errors
11 30
261 7,511
- -
6.2 0.2
13 days ago over 2 years ago
Go Go
BSD 2-clause "Simplified" License BSD 2-clause "Simplified" License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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

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
    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.

errors

Posts with mentions or reviews of errors. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-11-29.

What are some alternatives?

When comparing exhaustive and errors you can also consider the following projects:

zerolog - Zero Allocation JSON Logger

autoflags - Populate go command line app flags from config struct

go-multierror - A Go (golang) package for representing a list of errors as a single error.

logrus - Structured, pluggable logging for Go.

bitio - Optimized bit-level Reader and Writer for Go.

Testify - A toolkit with common assertions and mocks that plays nicely with the standard library

errorx - A comprehensive error handling library for Go

uuid - Generate, encode, and decode UUIDs v1 with fast or cryptographic-quality random node identifier.

go-chat-bot - IRC, Slack, Telegram and RocketChat bot written in go

vfs for golang - Virtual filesystem library written in golang

chi - lightweight, idiomatic and composable router for building Go HTTP services

Miniflux - Minimalist and opinionated feed reader