exhaustive
errors
Our great sponsors
exhaustive | errors | |
---|---|---|
11 | 30 | |
271 | 7,511 | |
- | - | |
6.2 | 0.2 | |
6 days ago | over 2 years ago | |
Go | Go | |
BSD 2-clause "Simplified" License | BSD 2-clause "Simplified" 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.
errors
-
Show HN: Error return traces for Go, inspired by Zig
Can you explain why we should this over https://github.com/pkg/errors?
-
Cant wait for less verbose error handling
The pkg/errors package offers some nice add-ons for easier error handling. Too bad it was put into maintenance mode pending whatever changes/improvements are coming in Go 2.
- Error handling and serializing
-
isse for go path in neovim
I can't figure out the issue so here for some help, I am using `neovim/nvim-lspconfig` my `gopls` doesn't recognise external paths such as `github.com/pkg/errors` , it throws error`could not import github.com/pkg/errors (cannot find package "github.com/pkg/errors" in any of /usr/local/go/src/github.com/pkg/errors (from $GOROOT) /Users/ra compiler (BrokenImport)\`
-
What am I supposed to be doing with errors?
Also - there are some error handling utils that allow you to wrap errors before passing: https://github.com/pkg/errors
-
Go error handling is not verbose but the error handling itself.
Should've been something like errors.Newf("failed to foofoo %s", foo) instead and preferably never invent %w but have some controlled way to wrap like errors.Wrapf(err, "failed to foofoo %s", foo) that was in ye olde github.com/pkg/errors.
-
How to wrap the error best?
Prefer using errors.Wrap and errors.Wrapf from https://github.com/pkg/errors . It's frozen because they don't want to add features, waiting for a re-write of error handling in Go2.
- mdobak/go-xerrors: Yet another error handling library.
-
Getting at the type of error after it has been wrapped with errors.Wrap
Im using zerolog and in order to get the stack trace for my error I have to wrap my error in errors.Wrap from "github.com/pkg/errors".
-
When ia a good time to panic?
And for "real programs" you can use https://github.com/pkg/errors (if you want stack traces)
What are some alternatives?
golangci-lint - Fast linters Runner for Go
zerolog - Zero Allocation JSON Logger
reposurgeon
autoflags - Populate go command line app flags from config struct
Ionide-vim - F# Vim plugin based on FsAutoComplete and LSP protocol
go-multierror - A Go (golang) package for representing a list of errors as a single error.
go-optional - A library that provides Go Generics friendly "optional" features.
logrus - Structured, pluggable logging for Go.
ionide-vscode-fsharp - VS Code plugin for F# development
bitio - Optimized bit-level Reader and Writer for Go.
enumcheck - Allows to mark Go enum types as exhaustive.
Testify - A toolkit with common assertions and mocks that plays nicely with the standard library