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. …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
  2. 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
  3. see also https://github.com/golang/go/discussions/54245
    comment by ikiris · 2023-07-17 · in Coroutines for Go
  4. There is a ticket in Go's repo about this: https://github.com/golang/go/issues/51900
  5. …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
  6. …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
  7. 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…
  8. 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
  9. …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
  10. 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
  11. …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
  12. …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
  13. 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
  14. 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
  15. …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
  16. 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
  17. …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
  18. 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
  19. 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
  20. 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
  21. …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?
  22. …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
  23. Example of assembly in Go source code: https://github.com/golang/go/blob/master/src/crypto/md5/md5b...
  24. …their intentions and after consulting the community, they changed it to be opt-in instead. https://github.com/golang/go/issues/58894
  25. 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
  26. …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
  27. 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
  28. Just the toolchain. https://github.com/golang/go/issues/58894
  29. …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
  30. …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
  31. …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...
  32. …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…
  33. …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
  34. …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...
  35. …users' explicit consent is a bad idea, no matter how "non-intrusive" and "helpful" it is. [0] https://github.com/golang/go/discussions/58409
    comment by bheadmaster · 2023-04-27 · in Dropbox telemetry can't be disabled
  36. https://github.com/golang/go/issues/44226 If you're just looking for signs of consensus that issue describes why the Go pgp package is deprecated - it is very critical of pgp. Interesting read too.
    comment by burnished · 2023-04-21 · in Introducing 'Trusted Publishers'
  37. Still waiting on io_uring in the Go stdlib: https://github.com/golang/go/issues/31908 "Unplanned"
    comment by candiddevmike · 2023-04-12 · in Using io_uring for network I/O
  38. …follow-up features that would have been there at 1.0 if generics were added, e.g. iterators [1]: https://github.com/golang/go/discussions/48287
  39. …some issues [0] which I assume were caused by the same $GOPATH change you're talking about. [0] https://github.com/golang/go/issues/44840#issuecomment-12896...
  40. …As a result, defer can now be used in performance-critical code without overhead concerns. EDIT: https://github.com/golang/go/issues/14939 I believe is the main tracking bug for this.
  41. …Funnily the actual Go JSON decoder code ends up doing something similar during scanning: https://github.com/golang/go/blob/master/src/encoding/json/d...
    comment by donio · 2023-03-29 · in Awk Technical Notes
  42. OP here, How are you doing caching without a mod time? https://github.com/golang/go/issues/44854 Are you re-naming or hashing for cache clearing?
  43. …this from the Go side. The original issue was this one: runtime: tight loops should be preemptible https://github.com/golang/go/issues/10958 > it's possible to write a tight loop (e.g., a numerical kernel or a spin on an atomic) with no…
  44. Related: "The slog / Structured Logging Proposal is Accepted" https://github.com/golang/go/issues/56345#issuecomment-14705...
  45. It is (non-sarcastically) good to see the Go team changing their opinion on the usefulness of it: https://github.com/golang/go/issues/16537
    comment by aleksi · 2023-03-09 · in Code coverage for Go integration tests
  46. …code execution during `go get`. Now - there have been bugs which permit code execution (like https://github.com/golang/go/issues/22125 ) but they are treated as security vulnerabilities and bugs. Of course, you're right about Python.
  47. …or gzipped file instead[1]. [0]: https://tinygo.org/docs/reference/lang-support/stdlib/ [1]: https://github.com/golang/go/wiki/WebAssembly#reducing-the-s...
  48. …and being so adamant about it made me reconsider the extent I'm going to use Go in the future. [0]: https://github.com/golang/go/discussions/58409#discussioncom...
  49. How come https://github.com/golang/go/discussions/58409 Blabs on about the bureaucratic/ policy ends of collecting data from me and NOT what they want to impact? Geez not even one example of where a little data could've helped golang…
  50. …information they need to work efficiently and effectively " which does not mention project size. https://github.com/golang/go/discussions/58409 I'm guessing he implicitly means "larger open source projects" but his statement reads like an…
    comment by uberman · 2023-02-13 · in Google killed my hope and my dreams