Goenums: Type Safe Enum Generator for Go

Re:Goenums: Type Safe Enum Generator for Go by HideousKojima on Saturday April 26, 2025 @06:28PM (#43807781)

>The key point here is our programmers are Googlers, they’re not researchers. They’re typically, fairly young, fresh out of school, probably learned Java, maybe learned C or C++, probably learned Python. They’re not capable of understanding a brilliant language but we want to use them to build good software. So, the language that we give them has to be easy for them to understand and easy to adopt.

- Rob Pike

[ Parent | on HN ]

Re:Goenums: Type Safe Enum Generator for Go by tyre on Saturday April 26, 2025 @08:02PM (#43808322)

sorry is the point here that enums are too complicated to understand?

[ Parent | on HN ]

Re:Goenums: Type Safe Enum Generator for Go by pjmlp on Sunday April 27, 2025 @02:09AM (#43809791)

Apparently, like most modern language features in the last 50 years or so.

[ Parent | on HN ]

Re:Goenums: Type Safe Enum Generator for Go by lionkor on Saturday April 26, 2025 @07:07PM (#43808080)

So they made it easy to have data races in a language all about concurrency, bravo. Not buying it.

[ Parent | on HN ]

Re:Goenums: Type Safe Enum Generator for Go by ad_hockey on Sunday April 27, 2025 @05:44AM (#43810635)

It's possible to have data races if you ignore the language conventions[1]. But even then, Go has provided an effective data race detection tool since 1.1: https://go.dev/blog/race-detector

I've been using Go on a large codebase for a number of years, and I haven't found data races to be a problem in practice.

[1] https://go.dev/doc/effective_go#sharing

[ Parent | on HN ]

Re:Goenums: Type Safe Enum Generator for Go by lionkor on Sunday April 27, 2025 @04:07PM (#43814699)

That's fantastic, good job! "Just be good enough at your job" is why C++ is fully concurrency- and memory safe, too. But, you know, its not, that's not how juniors use it, and boy do they write a lot of codebases I end up maintaining.

[ Parent | on HN ]