Comment by knorker

Yeah I've had specific use cases when I need to use syscall. I mean... if there weren't use cases for syscall then it wouldn't exist.

But not only is syscall an example of portability done wrong for APIs, as I said it's also an example of it being implemented in a dumb way causing needless work and breakage.

Syscall as implementation leads by bad example because it's the only method Go supports.

Checking for GOARCH+GOOS tuple equality for portable code is a known anti pattern, for reasons I've said and other ones, that Go still decided to go with.

But yeah, autotools scripts often check for way more things than actually matter. Often because people copy paste configure.ac from another project without trimming.