Re:Expectations for generics in Go 1.18
by eweise on Thursday October 28, 2021 @08:54AM
(#29025499)
Its only hard to read because you don't know the language, otherwise, its fairly straightforward. Although the Applicative type would require some research. I would much rather use a language like this, that can create enough abstraction to enforce consistency throughout the codebase, rather than relying on boilerplate conventions. Just had a bug this week in Go where a previously defined "err" variable was re-used instead of creating yet another "err" variable, which caused the actual error never to get checked.
[ Parent
| on HN ]
There are no comments on this comment yet.