Hacker News Reader

Comment by mappu | Hacker News Reader

(2016)

The versioning and slice sorting have since been solved, by go.mod and sort.Slice respectively.

The problem with "Make it an error to not initialise a struct field" is you lose source compatibility when adding new struct fields.

View on HN

> The problem with "Make it an error to not initialise a struct field" is you lose source compatibility when adding new struct fields.

If you allow the struct definition to specify a default value then the struct author can set default in the cases where there is a sensible default, and leave it compile-time incompatible in the cases where there really is no good default and the person doing the upgrade needs to make a decision.

That is already possible by exposing a `New` function and making the struct itself unexposed; are you suggesting syntax should be added to provide default values to struct fields? Because there is high resistance (which I agree with btw) to adding additional syntax and constructs to the language.

> That is already possible by exposing a `New` function and making the struct itself unexposed;

I thought Go didn't allow functions with default argument values either?

Still no official debugger though. Delve is just full of bugs.

Just do as the Head of Marketing from previousEmployer suggested and "leave out the bugs"

Revolutionary thinking right there

That's next-level.

Was he being ironic, or serious? Love to hear more.

"Head of Marketing". He was probably serious.

delve (through vscode-go) has worked fine from my perspective

Reply on news.ycombinator.com