go101
An up-to-date (unofficial) knowledge base for Go programming self learning (by go101)
errors
Simple error handling primitives (by pkg)
| go101 | errors | |
|---|---|---|
| 41 | 30 | |
| 5,385 | 7,511 | |
| - | - | |
| 7.3 | 0.2 | |
| 5 days ago | over 2 years ago | |
| HTML | Go | |
| GNU General Public License v3.0 or later | 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.
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.
go101
Posts with mentions or reviews of go101.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-04-17.
-
The Journey Ahead: My 6-Month Plan to Master GoLang
Go101: An in-depth guide that explores Go's internals, perfect for understanding the language at a deeper level.
- All books in Go 101 series have been updated to Go 1.21
-
Deconstructing Go Type Parameters
Go101 is a jewel of a resource. It’s a spec written by an impartial observer not worried about trying to make golang look good but instead giving you the understanding to avoid all the edge cases
https://go101.org/
- How to learn go from zero?
-
Perfect Golang learning roadmap
How about this: https://go101.org/ might help :)
-
Resources for an experienced programmer wanting to learn Go
Go 101 books, which cover every corner of the language itself (syntax, semantics, compiler and runtime implementation) and make more detailed explanations than the official docs in several points. (Author here)
-
Golang string concatenation performance comparison
Sometimes, reality and theory are not consistent: https://github.com/go101/go101/blob/master/pages/optimizations/code/4-string-and-byte-slice/concat-with-stack-byte-slice_test.go
-
Language specification or just a detailed book on the internals (focused on usage rather than compiler creation)?
How about go 101 ?
- I know JavaScript and looking for Go learning resource
-
Senior engineer here trying to pick up Go for jobs. What resources can you recommend me to cover as much ground as possible
https://go101.org/ - read this.
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.
-
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?
When comparing go101 and errors you can also consider the following projects:
go - The Go programming language
zerolog - Zero Allocation JSON Logger
rustig - A tool to detect code paths leading to Rust's panic handler
autoflags - Populate go command line app flags from config struct
go-perfbook - Thoughts on Go performance optimization
go-multierror - A Go (golang) package for representing a list of errors as a single error.
gopl.io - Example programs from "The Go Programming Language"
logrus - Structured, pluggable logging for Go.
mangagram - A Telegram bot for new manga chapter alerts. Search for your favorite titles and subscribed to them for alerts.
bitio - Optimized bit-level Reader and Writer for Go.
go-sumtype - A simple utility for running exhaustiveness checks on Go "sum types."
Testify - A toolkit with common assertions and mocks that plays nicely with the standard library