/explore
|
You are here 
|
dave.cheney.net | ||
| | | | |
alnvdl.github.io
|
|
| | | | | A bit of history, a bit of atonement, a bit of shameless self-promotion. | |
| | | | |
www.4async.com
|
|
| | | | | golang/x/exp?xerrors?golang/x/exp?errors?\nPackage errors implements functions to manipulate errors. This package implements the Go 2 draft designs for error inspection and printing ?github.com/pkg/errors?\n?error? ?github.com/pkg/errors?Go?\npackage main import ( "fmt" "golang.org/x/exp/xerrors" ) func raiseError() error { return xerrors.New("a new error") } func main() { err := xerrors.Errorf("raiseError: %w", raiseError()) fmt.Println(err) } ?\nraiseError: a new error ?github.com/pkg/errors?xerrors.Errorf?errors.Wrap? ?%w?\n?Is?As?Opaque?Unwrap?\nvar ( ErrBase = xerrors.New("a new error") ) func main() { err := xerrors.Errorf("raiseError: %w", ErrBase) fmt.Println(ErrBase == ErrBase) // fmt.Println(err == ErrBase) // ?ErrBase? fmt.Println(xerrors.Is(err, ... | |
| | | | |
grosser.it
|
|
| | | | | Why go does not have nice backtraces Collecting stacktraces is expensive, so the core language will never implement them for everything.If you need your code to be highly performant then consider making a error wrapper that can be turned on/off based on a environment variable. Simple fix import github.com/pkg/errors and use it instead of errors... | |
| | | | |
chipx86.blog
|
|
| | | Here's a very quick, not exactly comprehensive tutorial on building Docker images using multiple hosts (useful for building multiple architectures). If you're an expert on docker buildx, you may know all of this already, but if you're not, hopefully you find this useful. We'll make some assumptions in this tutorial: We want to build a... | ||
