Comment by Svip 10 months ago The consumer didn't, but the error in the example is typed, it's called `MaxBytesError`. 2 comments Svip Reply eptcyka 10 months ago Matching the underlying type when using an interface never feels natural and is definitely the more foreign part of Go's syntax to people who are not super proficient with it. Thus, they fall back on what they know - string comparison. simiones 10 months ago Only since go 1.19. It was a stringy error since go 1.0 until then.
eptcyka 10 months ago Matching the underlying type when using an interface never feels natural and is definitely the more foreign part of Go's syntax to people who are not super proficient with it. Thus, they fall back on what they know - string comparison.
Matching the underlying type when using an interface never feels natural and is definitely the more foreign part of Go's syntax to people who are not super proficient with it. Thus, they fall back on what they know - string comparison.
Only since go 1.19. It was a stringy error since go 1.0 until then.