doc: Effective Go section about Errors uses type assertion without mentioning errors.As #45535
Labels
Documentation
Issues describing a change to documentation.
NeedsDecision
Feedback is required from experts, contributors, and/or the community before a change can be made.
Milestone
What version of Go are you using (
go version
)?n/a
Does this issue reproduce with the latest release?
n/a
What operating system and processor architecture are you using (
go env
)?n/a
What did you do?
Read about errors in "Effective Go"
What did you expect to see?
Examples that use the current best way of inspecting concrete error values or acknowledgment that there is a better way with a reference to details about the alternatives.
What did you see instead?
Use of a type assertion in the style typically used with Go 1.12 and earlier without any mention of
errors.As
available since Go 1.13.The text was updated successfully, but these errors were encountered: