11 ms·
When I clicked on the link to codebases relying on the specific error string, I was expecting to see random side projects. Wasn't expecting to see Grafana and C
by apitman 2y ago
When I clicked on the link to codebases relying on the specific error string, I was expecting to see random side projects. Wasn't expecting to see Grafana and Caddy on the list.
- Cthulhu_ 2y agoNever underestimate the mediocrity of known large codebases, lol. (just kidding, they're not mediocre, but they're not infallible or perfect either)
- apitman 2y agoThis instance doesn't necessarily indicate they did anything wrong. See sibling.
- gwd 2y agoTo be fair to those projects, the type was introduced only three years ago: https://github.com/golang/go/pull/49359/files https://github.com/golang/go/pull/49359/files Before that, doing a string compare was basically the only way to detect that specific error. That was definitely an omission on the part of the original authors of the stdlib code; I don't it should be classified as "Hyrum's Law".
- apitman 2y agoYeah I don't doubt it was the best option. Just a bit surprised.
- mholt 2y agoHey Anders; Francis notified us of this today. I didn't realize a proper type had been created. We'll update our code.