proposal: all: Is there a plan to wrap more errors?

[hopehook]

To be honest, the error mechanism of the current go language is still quite confusing, and it is impossible to judge the underlying errors well.

Not sure if there are plans to keep improving the error wrapping mechanism throughout the language.
If there is an overall plan, maybe this problem can be solved faster.

For the user, the completed error wrapping mechanism is indeed the most important.

Here are some related open issues and CLs of package net/http

• proposal: net: add Is method to errCanceled and errTimeout so that they match context.{Canceled,DeadlineExceeded} net: make errCanceled and errTimeout be "errors.Is" context.Canceled and context.DeadlineExceeded #51428

• issue: net/http: wrap more errors? net/http: wrap more errors? #36713

• issue: net/http: Client does not wrap context errors net/http: Client does not wrap context errors #50856

And more:

• proposal: encoding/json: add support of wrapped error in addErrorContext function proposal: encoding/json: add support of wrapped error in addErrorContext function  #45449

• issue: crypto/tls: wrap handshake errors crypto/tls: wrap handshake errors #48151

• issue: x/crypto/ssh: Wrap error in NewClientConn x/crypto/ssh: Wrap error in NewClientConn #45207

• issue: database/sql: error not wrapped database/sql: error not wrapped #44635

[mdlayher]

This seems broad and unactionable compared to the individual issues linked here. Closing.

[hopehook]

This seems broad and unactionable compared to the individual issues linked here. Closing.

This is a friendly suggestion, I hope the go team can take it seriously and raise the priority.

Without an overall proposal, improving it maybe be very slow.