Down the Golang Nil Rabbit Hole

Re:Down the Golang Nil Rabbit Hole by kodah on Tuesday March 30, 2021 @01:02AM (#26631406)

> It's inability to deal with cyclic references, the lack of overloading, the lack of package-level visibility and the lack of static functions all contribute to a lot of ceremony.

After 4 years of Go, this is usually a design thing. Once I figured out how to separate and isolate domains of interest better, I stopped running into these issues entirely. My code, in and outside of Go, is much better for it. I also learned that much of "thread-safe" programming is taught this way, which makes sense.

[ Parent | on HN ]

Re:Down the Golang Nil Rabbit Hole by christophilus on Tuesday March 30, 2021 @06:45AM (#26633070)

F# has similar constraints, and gets similar complaints, and yet advocates (like I) think it’s a feature, not a bug. Most problems can be decomplected, and I like that Go enforces this particular constraint.

[ Parent | on HN ]

Re:Down the Golang Nil Rabbit Hole by wizhi on Tuesday March 30, 2021 @04:30AM (#26632304)

Do you possibly have any example projects you would be willing to share?

I've been getting into Go for the past couple of months, but I still struggle with this.

[ Parent | on HN ]