|
You are here |
infinitedigits.co | ||
| | | | |
kaveh.page
|
|
| | | | | Add separator lines for a more legible bash terminal | |
| | | | |
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, ... | |
| | | | |
serverascode.com
|
|
| | | | | A techno-blog for our techno-times | |
| | | | |
parsiya.net
|
|
| | | [AI summary] A post by a security engineer details a subtle bug in Go code where dependence on system architecture (32-bit vs 64-bit) caused an integer overflow during a type conversion, leading to unexpected logic flow and security implications. | ||