Lies we tell ourselves to keep using Golang

Re:Lies we tell ourselves to keep using Golang by euroderf on Tuesday November 26, 2024 @04:18AM (#42243929)

This. And there is one technique that would help in this.

Too often I see code like "xyz := pkg1.SomeFunc(a, b, c)" that makes xyz's type non-evident, especially when interfaces are involved.

Please write Go code like

  var xyz pkg2.SomeType

  xyz = pkg1.SomeFunc(a, b, c)

My 0.02€, YMMV.

[ Parent | on HN ]

Re:Lies we tell ourselves to keep using Golang by maleldil on Tuesday November 26, 2024 @05:05AM (#42244238)

I don't get it. Why not use a code editor that shows the inferred type on hover?

[ Parent | on HN ]

Re:Lies we tell ourselves to keep using Golang by zgiber on Tuesday November 26, 2024 @05:31AM (#42244411)

That should not be an issue, unless the code is written in notepad. As for interfaces, a better approach is to return struct and accept interface in your functions wherever it is possible.

[ Parent | on HN ]

Re:Lies we tell ourselves to keep using Golang by linhns on Thursday November 28, 2024 @10:25PM (#42270543)

Sometimes it's better to to return interfaces, like contract style programming.

[ Parent | on HN ]