←back to thread

Hyrum's Law in Golang

(abenezer.org)
181 points thunderbong | 1 comments | 21 Nov 24 07:12 UTC | HN request time: 0.838s | source
Show context
raverbashing ◴[21 Nov 24 08:39 UTC] No.42202306[source]▶
It's like an inverted game of cat and mice

1 - Lang/OS/Lib developer puts out a quirky or buggy API (or even just an ok API)

2 - Developers rely on a quirky, weird or unexpected side effect because it's easier/more obvious or it just works this way due to a bug

3 - Original developer can't fix it because it would break compatibility

4 GOTO 1

replies(2): >>42202332 #>>42202389 #
Cthulhu_ ◴[21 Nov 24 08:57 UTC] No.42202389[source]▶
And this isn't even quirky/buggy, it's just the string representation of an error. That said, Go took a while to improve its core error mechanisms and add utilities for matching errors by type instead of its string representation.
replies(1): >>42203387 #
1. simiones ◴[21 Nov 24 11:50 UTC] No.42203387[source]▶
In this case, it really is - because until Go 1.19, that function simply returned `errors.New("http: request body too large")`. So until Go 1.19, there really was no other way to check if this error occurred than `err.String() == "http: request body too large"`. Even if we had had errors.Is/As earlier, it wouldn't have helped in this case.