Hacker GitHub

← All repos

golang/go

View on GitHub ↗ ★ 139,735 Go

The Go programming language

1,947 mentions on Hacker News by 1,181 people: 291 stories, 1,656 comments · first 2014-12-08 · latest 2026-10-22

Mentions per year 1,947 mentions · busiest year 2023 (221)
20082026
  1. There used to be one, but they took it out. https://github.com/golang/go/issues/28152
  2. …interfaces should never be used until there is a clear need. CodeReviewComments covers the basics: https://github.com/golang/go/wiki/CodeReviewComments#interfa... I wrote an insanely long rant about this with thorough examples using the…
  3. i think the parent was referring to https://github.com/golang/go/issues/45970
    comment by malaya_zemlya · 2021-11-22 · in Rust Moderation Team Resigns
  4. …any case, it seems like an issue was opened proposing something like that a couple of years ago ( https://github.com/golang/go/issues/23027 ), and Russ Cox responded that the JSON package is basically done, but you could either fork it and…
  5. There is also a gem inside from rsc: https://github.com/golang/go/issues/49569#issuecomment-96898... That's quality thinking!
  6. ▲ 2
    Go 1.18 compile time may be about 18% slower than Go.17
    story by jhoechtl · 2021-11-16 · 2 comments
  7. …exhaustive type switches would bring Go something close to the sum types of Rust and Swift. [0]: https://github.com/golang/go/issues/45346
    comment by ibraheemdev · 2021-11-15 · in A rough proposal for sum types in Go (2018)
  8. …are endless! They are a set of limited yet unvalidated translation DSLs stuffed into a string. https://github.com/golang/go/search?p=4&q=struct+tags&type=i... Personally I think the language would be better without them, but it's too late…
    comment by grey-area · 2021-11-10 · in Twelve Years of Go
  9. …be less clumsy once it arrives, but I strongly believe it is best to take it slow for now." [0] https://github.com/golang/go/issues/48918
    comment by kgeist · 2021-11-09 · in Upcoming Features in Go 1.18
  10. https://github.com/golang/go/issues/32437
    comment by morelisp · 2021-11-09 · in Upcoming Features in Go 1.18
  11. …| grep fork vfork() = 15 edit 2: here's a similar tale from go, replacing use of fork in fork/exec: https://github.com/golang/go/issues/5838 https://go-review.googlesource.com/c/go/+/37439/ https://about.gitlab.com/blog/2018/01/23/how-a-fix…
  12. This issue has been raised before, such as at https://github.com/golang/go/issues/20209 (I was reminded of that by https://twitter.com/peter_szilagyi/status/145515080347229798... ). There is some other interesting discussion there.
  13. …but never canceled. At least, that seems to be the behavior I see in the implementation here: https://github.com/golang/go/blob/master/src/context/context... So in this case, errgroup probably doesn't have a choice and needs to call…
    comment by reltuk · 2021-10-29 · in Error handling with errgroups
  14. …many cases it is possible to write code that does what generics would enable, if less smoothly. [1] https://github.com/golang/go/commit/dd64f86e0874804d0ec5b713...
    comment by tcard · 2021-10-28 · in Expectations for generics in Go 1.18
  15. The hybrid approach is absolutely implemented: https://github.com/golang/go/blob/master/src/cmd/compile/int...
    comment by mseepgood · 2021-10-28 · in Expectations for generics in Go 1.18
  16. …to the proposals for shorter Go error handling The community didn't like it and it was declined: https://github.com/golang/go/issues/32437#issuecomment-51203...
    comment by mseepgood · 2021-10-28 · in Expectations for generics in Go 1.18
  17. Related discussion from 10 days ago: go: don't change the libraries in 1.18 https://github.com/golang/go/issues/48918 https://news.ycombinator.com/item?id=28895440
    comment by oefrha · 2021-10-28 · in Expectations for generics in Go 1.18
  18. …your machine should still remain uncompromised. They release CVEs for any issues here (such as https://github.com/golang/go/issues/29231 ). Of course, if you run the code you compiled, that is unsafe, but just compiling it is supposed to…
  19. update: they missed implementing this and now go1.17 will be required to bootstrap go1.19+. https://github.com/golang/go/issues/44505#issuecomment-94259...
  20. …go1.4 up to 1.17 need to be built with 1.4. From 1.18 on, they need to be built with 1.16. See https://github.com/golang/go/issues/44505 .
  21. …one of the authors of TLS 1.3. He has refused to allow for configuration of TLS 1.3 ciphers in Go: https://github.com/golang/go/issues/29349 Thanks to this decision: if a particular cipher is found to be weak or vulnerable, people using Go…
  22. ▲ 2
    Sync: ExampleWaitGroup includes an porn website url · Issue #48886 · Golang/go
    story by xojoc · 2021-10-22 · 1 comment
  23. …would break backward compat. So there is basically an unfixable bug sitting in go html templates. https://github.com/golang/go/issues/9200
    comment by shp0ngle · 2021-10-17 · in Go: Don't Change the Libraries in 1.18
  24. ▲ 183
    Go: Don't Change the Libraries in 1.18
    story by dbattaglia · 2021-10-17 · 122 comments
  25. …other perf ideas from LuaJIT) - The stop-the-world implementation is influenced by Go's design ( https://github.com/golang/go/blob/fad4a16fd43f6a72b6917eff65... )"
    comment by typical182 · 2021-10-15 · in A viable solution for Python concurrency
  26. ▲ 4
    Go: Don't Add Generics to Go's Core Libraries in 1.18
    story by 0xedb · 2021-10-15 · 1 comment
  27. ▲ 14
    Go: Don’t change the libraries in 1.18
    story by todotask · 2021-10-12 · 0 comments
  28. …as a major problem[1][2]. [1] https://go.googlesource.com/proposal/+/master/design/go2draf... [2] https://github.com/golang/go/issues/32437#issuecomment-51203...
    comment by unscaled · 2021-10-04 · in Things Go needs more than generics
  29. …code. So you get zero readability gains at the price of two significant readability losses. --- [1] https://github.com/golang/go/issues/40432 [2] https://go.googlesource.com/proposal/+/master/design/go2draf... [3]…
    comment by unscaled · 2021-10-04 · in Things Go needs more than generics
  30. …that can be a nice evolution. [1] https://github.com/romshark/Go-1-2-Proposal---Immutability [2] https://github.com/golang/go/issues/27975
    comment by jicea · 2021-10-04 · in Things Go needs more than generics
  31. …it didn't know, but that caused issues on musl-based systems which used a different mechanism ( https://github.com/golang/go/issues/35305 ). And it cannot ever be fully static on glibc-based systems, since there's always the chance of…
  32. …slice tricks will soon be replaced with "container/slice" (although you'll still need a few)! [1] https://github.com/golang/go/issues/45955
    comment by parhamn · 2021-10-03 · in Effective Go
  33. …and all external dependencies should always be distributed in source-form, not as binaries (e.g. https://github.com/golang/go/issues/2775 ).
  34. Also https://github.com/golang/go/wiki/CodeReviewComments
    comment by louis-paul · 2021-10-03 · in Effective Go
  35. A bunch of other docs I've looked up number of times and found handy: - Slice tricks: https://github.com/golang/go/wiki/SliceTricks - Rest of the Golang Github Wiki: https://github.com/golang/go/wiki#additional-go-programming-... - Spec -…
    comment by oxplot · 2021-10-03 · in Effective Go
  36. - Go Code Review Comments: https://github.com/golang/go/wiki/CodeReviewComments
    comment by rob74 · 2021-10-03 · in Effective Go
  37. ▲ 3
    Go Generics 2x faster than stdlib for sorting
    story by dcu · 2021-09-24 · 0 comments
  38. ▲ 2
    Go container/set: new package to provide a generic set type
    story by 0xedb · 2021-09-23 · 1 comment
  39. ▲ 2
    Dev.fuzz (fuzzing) merged in Golang tip
    story by mfrw · 2021-09-21 · 0 comments
  40. In the spirit of this, the Go project has a "common code review comments" document ( https://github.com/golang/go/wiki/CodeReviewComments ) - topics that come up frequently when reviewing pull requests. Reading these can certainly help you…
  41. ▲ 126
    Golang: How to Update APIs for Generics
    story by 0xedb · 2021-09-15 · 63 comments
  42. …whose code I'm reviewing are competent, idiomatic go programmers who follow go's style guide ( https://github.com/golang/go/wiki/CodeReviewComments ) to the extent that it exists. I find it far more difficult to tease out what a stanza of…
    comment by joshuamorton · 2021-09-14 · in Go’ing Insane: Endless Error Handling
  43. …require a SAT-solver (dependency hell is NP-complete https://research.swtch.com/version-sat ) https://github.com/golang/go/issues/24301 https://go.googlesource.com/proposal/+/master/design/24301-v... https://research.swtch.com/vgo…
  44. …a proposal in motion to do exactly this, with support among both devs and the language maintainers: https://github.com/golang/go/issues/21182#issuecomment-54241...
    comment by jesseduffield · 2021-09-14 · in Go’ing Insane: Endless Error Handling
  45. ▲ 1
    Golang: Doc comment revisions: headings, lists, and links
    story by m90 · 2021-09-12 · 0 comments
  46. ▲ 1
    Go doc comment revisions: headings, lists, and links
    story by benhoyt · 2021-09-12 · 0 comments
  47. …would have just used type switches for efficiency -- it looks like it does for common cases ( https://github.com/golang/go/blob/d62866ef793872779c9011161e... ) but then falls back to reflect. I wonder why it doesn't just do all of that…
  48. …individual fields (though the common cases are done without reflect, using ordinary type switches: https://github.com/golang/go/blob/d62866ef793872779c9011161e... ).
  49. That was the second bug. The first bug was this one (CL sent on 2014-08-19 and merged on 2014-09-24): https://github.com/golang/go/issues/7978 https://codereview.appspot.com/131910043 I particularly like this comment: "Ping. Could somebody…
  50. …of Go is something I value a lot, so I don’t mind stop-gaps like this too much on balance. [0] https://github.com/golang/go/issues/20148 [1] https://github.com/golangci/golangci-lint
    comment by xh-dude · 2021-08-24 · in Error stack traces in Go with x/xerror