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. Go tried the same, and chose to let the user opt-in. https://github.com/golang/go/discussions/58409 The privacy design for Go was actually sound. https://research.swtch.com/telemetry-design
  2. …nobody ever actually ran the upstream version and or (2) downstream software is papering it over: https://github.com/golang/go/issues/21083
    comment by stefan_ · 2023-07-30 · in Musl 1.2.4 adds TCP DNS fallback
  3. …on Windows, not about what valid file names applications may encounter. Here's a counter-example: https://github.com/golang/go/issues/32334
    comment by skitter · 2023-07-25 · in Unicode is harder than you think
  4. …answers, but the runtime source has some pointers that would likely get you the answer you seek: https://github.com/golang/go/blob/master/src/runtime/HACKING... It sounds like blocking calls switch to a system stack and return the Go stack…
    comment by sharkbot · 2023-07-25 · in Threads and Goroutines
  5. This was referenced, which I thought was interesting: https://github.com/golang/go/issues/13492 golang cannot be compiled as a C static library with musl.
    comment by djoldman · 2023-07-21 · in How Turborepo is porting from Go to Rust
  6. …true. this is good code: https://github.com/torvalds/linux/blob/master/fs/file.c this is good code: https://github.com/golang/go/blob/master/src/strconv/atoc.go its formatted, commented, direct. the fact that you struggle with writing time…
  7. ▲ 3
    Go: Add range over int, range over func
    story by philosopher1234 · 2023-07-20 · 0 comments
  8. …a lot to say the least, to become 'mainstream', Golang actually has to embrace more use cases. https://github.com/golang/go/issues/47788
  9. …this, rf is still experimental and not complete: https://pkg.go.dev/rsc.io/rf . Example use case: https://github.com/golang/go/issues/46792 I much prefer the non-viral public/private attributes other languages use.
  10. …without allocating read buffers for the entire connection. I.e. a solution to problems discussed in https://github.com/golang/go/issues/15735 . Goroutines provide a great way to have non-blocking IO with synchronous code – but when it…
    comment by FZambia · 2023-07-18 · in Coroutines for Go
  11. …keeping the optimization of coroutines as a runtime implementation detail. I feel vindicated. :-) https://github.com/golang/go/discussions/56413#discussioncom...
    comment by earthboundkid · 2023-07-18 · in Coroutines for Go
  12. …with is a "push iterator", which are often much simpler to implement, but less flexible to use. See https://github.com/golang/go/discussions/56413 The OP is about converting a push iterator into a pull iterator efficiently by using…
    comment by aaronbee · 2023-07-17 · in Coroutines for Go
  13. This has been under discussion for a long time. https://github.com/golang/go/issues/43557 https://github.com/golang/go/discussions/56413 I'm not sure Russ's personal blog is any kind of official statement "this is what we're doing" yet?
    comment by morelisp · 2023-07-17 · in Coroutines for Go
  14. see also https://github.com/golang/go/discussions/54245
    comment by ikiris · 2023-07-17 · in Coroutines for Go
  15. There is a ticket in Go's repo about this: https://github.com/golang/go/issues/51900
  16. ▲ 30
    Codereview: Should the Go project stop importing GitHub PRs?
    story by nateb2022 · 2023-07-05 · 23 comments
  17. …casts use quadratic probing[1]). Or is it still advantageous for some reason? (Locality?) [1] https://github.com/golang/go/blob/03cd8a7b0e47f2141a1dbdad9f... via https://lukasatkinson.de/2018/interface-dispatch/
    comment by mananaysiempre · 2023-06-29 · in Solving “Two Sum” in C with a tiny hash table
  18. …your asking it to. For that matter it seems every go subcommand will do this (even --help [1]). [1] https://github.com/golang/go/issues/60956
  19. Curious what your concerns are? As of Go 1.21 the toolchain will be fully reproducible [ https://github.com/golang/go/issues/57120 ] and since the binaries will be distributed through the module system it'll be possible to verify that…
  20. Probably meant to link this. https://github.com/golang/go/discussions/60227 It’s an interesting discussion about making changes to the default router.
    comment by meblum · 2023-06-22 · in Go 1.21 Release Candidate
  21. …to add telemetry for these same reasons. This casts doubts on how well they're managing to do it. https://github.com/golang/go/discussions/58409
  22. You might be interested in this discussion https://github.com/golang/go/discussions/6022 about http serve mux.
    comment by meling · 2023-06-22 · in Go 1.21 Release Candidate
  23. …the zero value. The bug doesn't seem to discuss use cases for it either. The most I could find is: https://github.com/golang/go/issues/56351#issuecomment-13326... Which boils down to "doing what clear(slice) does cannot be implemented…
    comment by esprehn · 2023-06-22 · in Go 1.21 Release Candidate
  24. …they ask "but WHY is it like this?" More information about loop capture here for those interested https://github.com/golang/go/discussions/56010
    comment by tastysandwich · 2023-06-22 · in Go 1.21 Release Candidate
  25. From the spec [1], it was because the loop doesn't work to clear a map with a NaN key. [1] https://github.com/golang/go/issues/56351
    comment by skybrian · 2023-06-21 · in Go 1.21 Release Candidate
  26. And adding that they already had support for ARM sha256 instructions https://github.com/golang/go/blob/master/src/crypto/sha256/s...
    comment by monocasa · 2023-06-21 · in Go 1.21 Release Candidate
  27. …in my experience. I hope the experimental fix makes it into the next version of Go by default. [0] https://github.com/golang/go/wiki/LoopvarExperiment
    comment by djsavvy · 2023-06-21 · in Go 1.21 Release Candidate
  28. In case anyone else was wondering what this is about, here's some useful background https://github.com/golang/go/issues/45453
    comment by als0 · 2023-06-21 · in Go 1.21 Release Candidate
  29. …gives a rationale. Using builtin functions lets them be variadic without allocating a slice. [0] https://github.com/golang/go/issues/59488
    comment by tjalfi · 2023-06-21 · in Go 1.21 Release Candidate
  30. No, it was a recent discussion, here: https://github.com/golang/go/issues/59488
    comment by philosopher1234 · 2023-06-21 · in Go 1.21 Release Candidate
  31. They discuss this here: https://github.com/golang/go/wiki/LoopvarExperiment#will-the... In fact, you can enable warnings/logs that indicate whether code that is affected by the loopvar experiment results in a stack-allocated or…
    comment by quacker · 2023-06-21 · in Go 1.21 Release Candidate
  32. It looks like sync/errgroup is a proposal, but not in the standard library (not yet, at any rate): https://github.com/golang/go/issues/57534
  33. …that more or less behave like Go's goroutines. That's just my honest opinion, that's all. [1] https://github.com/golang/go/issues/58894
    comment by stefanos82 · 2023-06-14 · in Ask HN: Any info on Go adoption in industry?
  34. …does. Exceptions are rare (golang is one of them and even for golang there are discussions: https://github.com/golang/go/issues/57644 ) > To say Kotlin doesn't have a future when it is one of the widest used languages is a stretch Well,…
    comment by valenterry · 2023-06-10 · in Zig language server and cancellation
  35. ▲ 2
    Should Golang have a built-in 'zero' function?
    story by gus_leonel · 2023-06-09 · 0 comments
  36. Example of assembly in Go source code: https://github.com/golang/go/blob/master/src/crypto/md5/md5b...
  37. …their intentions and after consulting the community, they changed it to be opt-in instead. https://github.com/golang/go/issues/58894
  38. A few places I look: - https://dev.golang.org/release#Go1.21 - might be the same info as https://github.com/golang/go/milestone/279 in a different form and here is a link to the draft release notes https://tip.golang.org/doc/go1.21
    comment by roesl027 · 2023-05-26 · in How to start a Go project in 2023
  39. …in Go. It’s a concrete proposal from the core Go team and seems to be on track for acceptance: https://github.com/golang/go/issues/60078 An implementation is already available on tip and in the upcoming Go 1.21 release behind a…
    comment by typical182 · 2023-05-24 · in How to start a Go project in 2023
  40. ▲ 3
    Enhance Golang Http.ServeMux Routing
    story by bamazizi · 2023-05-23 · 0 comments
  41. The post is about the cost of calling SetFinalizer. Looking at https://github.com/golang/go/blob/master/src/runtime/mfinal.... it seems to be doing a lot, not just storing a function pointer somewhere. There are bunch of validations on the…
    comment by ankurdhama · 2023-05-20 · in The absurd cost of finalizers in Go
  42. Just the toolchain. https://github.com/golang/go/issues/58894
  43. …that to some of the other proposals with a ton of backing that have been frozen for years (like https://github.com/golang/go/issues/49085 ) due to the core team disagreeing with the direction. Basically, there's a very obvious in group…
    comment by candiddevmike · 2023-05-17 · in Add opt-in transparent telemetry to Go toolchain
  44. ▲ 110
    Add opt-in transparent telemetry to Go toolchain
    story by gus_leonel · 2023-05-17 · 119 comments
  45. …but more generally, you can certainly use pre-modules Go code with current Go compilers. See e.g. https://github.com/golang/go/issues/37797 (a case of someone not RTFMing, but the response illustrates how it's done). If you just want to…
    comment by foldr · 2023-05-14 · in macOS Apps in Rust
  46. …traditional c-like "for ;;" loops, which at least will produce two surprises to old Go programmers: https://github.com/golang/go/issues/60078#issuecomment-15443...
  47. …created by closure follow the same rules as any other reference.) And the earlier proposal: https://github.com/golang/go/discussions/56010 gives an explicit reference (with an &) as its motivating example. So I still believe that the whole…
  48. …little I do know sounds at least similar. Heres the issue where they changed the backcompat policy: https://github.com/golang/go/issues/56986
    comment by philosopher1234 · 2023-05-12 · in Proposal: Less error-prone loop variable scoping
  49. …discussion, of how C# had gone through almost exactly the same change and how that went down: https://github.com/golang/go/discussions/56010#discussioncom...
  50. ▲ 85
    Proposal: Less error-prone loop variable scoping
    story by yujian · 2023-05-11 · 73 comments