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
AllStoriesComments NewestTopOldest
  1. …). This can lead to "fun" issues where the behavior between resolvers diverges, such as https://github.com/golang/go/issues/15419 .
    comment by dpifke · 2022-12-22 · in The life of a DNS query in Kubernetes
  2. …the original issue in the Golang repo about possible uses for a standard library hash function: https://github.com/golang/go/issues/21195 And you're right, the Trie implementation linked there was indeed a Hash-Array Mapped Tried:…
    comment by awmarthur · 2022-12-21 · in Hacking Go's runtime with generics
  3. …the time. It's almost certainly better nowadays. Hopefully the Go runtime starts doing it instead: https://github.com/golang/go/issues/31908
    comment by bradfitz · 2022-12-13 · in Userspace isn't slow, some kernel interfaces are
  4. …instead of googling them? Here, why ISO 8601 support was dropped (spoiler: it's an unparsable mess) https://github.com/golang/go/issues/734 Design mistake )))
    comment by divan · 2022-12-11 · in New in Go 1.20: wrapping multiple errors
  5. …change wasn't accepted, but this[1] alternative will be. That seems like a great change to me. [1]: https://github.com/golang/go/issues/51365
    comment by fideloper · 2022-12-11 · in New in Go 1.20: wrapping multiple errors
  6. …should greatly simplify debugging, and avoid the common generic "context canceled" errors. [1]: https://github.com/golang/go/issues/46273
    comment by imiric · 2022-12-11 · in New in Go 1.20: wrapping multiple errors
  7. …the problem is old and well-known, and has quite a few tickets open on the golang bug tracker: https://github.com/golang/go/issues/47979 - the attributes exposed by marshaling libraries are different from one library to the next... i mean…
    comment by ooninoob · 2022-11-27 · in Ask HN: What do you like/dislike about Golang?
  8. …at all my experience. I had the compiler panic on me for daring to run "go get", as described here: https://github.com/golang/go/issues/47979 This issue has now been closed, but there are several others open with the same symptoms. The…
    comment by ooninoob · 2022-11-27 · in Ask HN: What do you like/dislike about Golang?
  9. …in 2009ish, they doubled down on it. Here in 2022, they finally opened it back up for discussion. https://github.com/golang/go/discussions/56010
    comment by bb88 · 2022-11-26 · in The Origins of Python
  10. > what's missing from Go that makes that impossible? The language maintainers don't want to add it: https://github.com/golang/go/issues/19412
    comment by satvikpendem · 2022-11-23 · in Using Rust at a startup: A cautionary tale
  11. There are some folks working on porting SwissTable to Go: https://github.com/golang/go/issues/54766 What’s holding it back currently is coming up with a way to do incremental rehash, which Go’s current map provides.
    comment by aaronbee · 2022-11-20 · in Inside boost::unordered_flat_map
  12. Russ Cox explains in the issue why they don't want it to be a standard library function: https://github.com/golang/go/issues/56351#issuecomment-12914... "We talked about defining maps.Clear in #55002, but how? It would not be possible to…
    comment by mseepgood · 2022-11-19 · in Go 1.21 may have a clear(x) builtin
  13. …because it's a little bit outside the "mainstream path", and calls it "badly documented". [1]: https://github.com/golang/go/issues/26492 [2]: https://duckduckgo.com/?q=go+compile+static
    comment by Beltalowda · 2022-11-11 · in Thirteen Years of Go
  14. …as the Go project discovered (after having been warned multiple times) during the Sierra betas: https://github.com/golang/go/issues/16272 https://github.com/golang/go/issues/16606 That doesn't mean Apple goes outs of its way to break…
    comment by masklinn · 2022-11-09 · in Why is Rosetta 2 fast?
  15. …they do the default, nor consider the impact of other language changes on your micro-optimizations. https://github.com/golang/go/blob/master/src/runtime/map.go You also won't have `for k, v := range` iteration, but that is also likely…
    comment by morelisp · 2022-11-08 · in Maps and Memory Leaks in Go
  16. …as average load of a bucket; where buckets have a maximum load of 8; i.e. 81% full) (ref: https://github.com/golang/go/blob/go1.19.3/src/runtime/map.g... ) > I’ll assume … doubling on resize Indeed (ref:…
    comment by LukeShu · 2022-11-08 · in Maps and Memory Leaks in Go
  17. …should be filed for this, but one of the blog comments says this issue could be fixed by [1]. [1]: https://github.com/golang/go/issues/54766
    comment by cglong · 2022-11-08 · in Maps and Memory Leaks in Go
  18. …though, and keep as much code in golang as possible. [1] https://go.dev/ref/spec#Allocation [2] https://github.com/golang/go/blob/master/src/runtime/mgc.go#...
    comment by cookiengineer · 2022-11-07 · in Nvidia Security Team: “What if we just stopped using C?”
  19. This would be easier if there was an easy way to write the zero value, irrespective of type. https://github.com/golang/go/issues/19642 was a proposal to have e.g. return _, _, err as an alternative to e.g. return 0, "", err
    comment by mikelward · 2022-11-06 · in Thoughts on the “guard” proposal for Go's error handling
  20. I officially proposed this recently and it wasn’t well received: https://github.com/golang/go/issues/56165 The proposal the submitted article references has been inactive for years. After submitting proposals and looking at the existing…
    comment by gregwebs · 2022-11-06 · in Thoughts on the “guard” proposal for Go's error handling
  21. FYI there is a weekly review of a subset of open proposals here: https://github.com/golang/go/issues/33502
    comment by philosopher1234 · 2022-11-02 · in The Problem with Go
  22. …in Golang isn't actually reproducible with `lto` enabled. One issue is what I submitted here; https://github.com/golang/go/pull/53528 Another issue which I have been trying to debug is why the code snippet located here doesn't reproduce.…
    comment by Foxboron · 2022-11-01 · in Is my package reproducible yet?
  23. …conservative until 1.3[1][2][3]: the heap was precise, but the stack was conservative. [0] https://github.com/golang/go/issues/46787 [1] https://go.dev/doc/go1.3#garbage_collector [2] https://docs.google.com/document/d/1lyPIbmsYbXnpNj57a261…
    comment by masklinn · 2022-10-29 · in Why is D's garbage collection slower than Go's?
  24. It actually used to call this, but was changed in 2015: https://github.com/golang/go/commit/fd4dc91a96518fdbb47781f9... I'm not entire sure if I see the problem or follow why just using runtime·cmpstring is such a bad thing; doesn't seem…
    comment by Beltalowda · 2022-10-27 · in No safe efficient ways to do three-way string comparisons in Go
  25. It was previously implemented as a special internal function https://github.com/golang/go/commit/fd4dc91a96518fdbb47781f9... So, making it a simple Go function was more work (at least, as an individual change) because they could've left…
    comment by somekyle2 · 2022-10-27 · in No safe efficient ways to do three-way string comparisons in Go
  26. The optimal version does seem to exist here (per the comment too): https://github.com/golang/go/blob/d28bf6c9a2ea9b992796738d03... So the goal was to intentionally nerf Compare() to discourage code the golang authors considered less clear.…
    comment by esprehn · 2022-10-27 · in No safe efficient ways to do three-way string comparisons in Go
  27. https://github.com/golang/go/commit/fd4dc91a96518fdbb47781f9... I interpret this as replacing a strange but more optimal call to the runtime with a straight forward but less fast stdlib implementation. rsc's comment seems more like a todo…
    comment by throwawayabcdef · 2022-10-27 · in No safe efficient ways to do three-way string comparisons in Go
  28. Wouldn't the normal implementation for == check lengths? Edit: Never mind, it doesn't: https://github.com/golang/go/blob/d28bf6c9a2ea9b992796738d03... But checking lengths doesn't really help you: it only tells you when strings are not…
    comment by tylerhou · 2022-10-27 · in No safe efficient ways to do three-way string comparisons in Go
  29. Worth noting that Go's GC is written entirely in Go. https://github.com/golang/go/blob/master/src/runtime/mgc.go
    comment by throwaway894345 · 2022-10-26 · in Oracle Contributing GraalVM Community Edition Java Code to OpenJDK
  30. …For example the Go runtime and I think C# as well are written in their respective language. https://github.com/golang/go/tree/master/src/runtime https://github.com/dotnet/runtime
    comment by Thaxll · 2022-10-26 · in Oracle Contributing GraalVM Community Edition Java Code to OpenJDK
  31. …https://baremessages.org [2] https://lists.sr.ht/~sircmpwn/public-inbox/%3CCAFFTG-a-Vci%2... [3] https://github.com/golang/go/issues/20660
    comment by conaclos · 2022-10-22 · in Comparing Floating-Point Numbers Is Tricky (2017)
  32. Underlying issue in Go: https://github.com/golang/go/issues/49269
    comment by slow_typist · 2022-10-17 · in Gitea still blocking recent SSH clients
  33. …Go doesn’t have a good central repository for go libraries, I don’t have good numbers on this. [1] https://github.com/golang/go/issues/48918
    comment by indrora · 2022-10-07 · in Ask HN: Was it worth it for Go to add generics
  34. We have that! https://sourcegraph.com/github.com/golang/go/-/blob/src/net/... * Works cross-repositories, over our indexed corpus of 6M OSS repositories, or your private code * Multi-language (some projects at compiler accuracy, some at…
    comment by beyang · 2022-10-04 · in Steve Yegge Joins as Head of Engineering of Sourcegraph
  35. …wasm (~2019), Brotli was the best compression approach. eg 16MB uncompressed -> 2.4MB compressed https://github.com/golang/go/wiki/WebAssembly#reducing-the-s...
    comment by justinclift · 2022-10-03 · in Postgres WASM
  36. This is being considered for Go 2: https://github.com/golang/go/issues/19623 Personally I'm wary of it: it's not hard to think of adversarial scenarios where this could lead to OOM. On the other hand, adversarially overflowing an int can…
    comment by nemo1618 · 2022-09-30 · in New integer types I’d like to see
  37. Custom ranges will be possible at some point: https://github.com/golang/go/discussions/54245
    comment by eliasdaler · 2022-09-27 · in Go runtime: 4 years later
  38. https://github.com/golang/go/issues/36313
    comment by LukeShu · 2022-09-26 · in Go runtime: 4 years later
  39. …logging is too simple, lacks levels and structured-logging-style (currently actively discussed: https://github.com/golang/go/discussions/54763 ) 4. Low-level UDP networking is weak (soon to be fixed as they accepted this proposal:…
    comment by tomalaci · 2022-09-26 · in Go runtime: 4 years later
  40. …According to the Go devs, this is also the policy on Solaris-family OSs (Go uses libc there): https://github.com/golang/go/issues/24357#issuecomment-37300... AFAIK, it is only Linux which explicitly supports the kernel system call…
    comment by twic · 2022-09-21 · in Can I use a system call?
  41. …(the exact syscall jart used above an example!) because the go compiler emitted direct syscalls: https://github.com/golang/go/issues/16606
    comment by lgg · 2022-09-21 · in Can I use a system call?
  42. Go issue for adding WASI: https://github.com/golang/go/issues/31105
    comment by ainar-g · 2022-09-20 · in Wasmtime 1.0
  43. Similar issue for not noticing changes in /etc/localtime: https://github.com/golang/go/issues/28020
    comment by yencabulator · 2022-09-20 · in Finding the “second bug” in glibc’s condition variable
  44. It is part of POSIX: https://github.com/golang/go/issues/36822#issuecomment-57938... Also RFC 3986.
    comment by gunapologist99 · 2022-09-19 · in https://16777217/
  45. This has been part of POSIX for decades, but not in Golang net yet. :( https://github.com/golang/go/issues/36822
    comment by gunapologist99 · 2022-09-19 · in https://16777217/
  46. …the mailing list to see what the maintainers think the future of runtime tracing looks like. [0] https://github.com/golang/go/issues/41324#issuecomment-70379... [1] https://opentelemetry.io [2] https://ui.perfetto.dev/
    comment by chrsig · 2022-09-19 · in Fgtrace – The Full Go Tracer
  47. > This stupidity surfaces everywhere; here is a Go bug report for it: > https://github.com/golang/go/issues/21083 The irony that they proposed a fix in 2017 but never got around to actually implementing it...
    comment by ChickeNES · 2022-09-19 · in Finding the “second bug” in glibc’s condition variable
  48. …invalidate it, just to be sure. This stupidity surfaces everywhere; here is a Go bug report for it: https://github.com/golang/go/issues/21083
    comment by stefan_ · 2022-09-18 · in Finding the “second bug” in glibc’s condition variable
  49. …large scale use cases. There is a more-than-6-year-old proposal to introduce non-blocking I/O API ( https://github.com/golang/go/issues/15735 ) but so far it's not gaining much traction. Maybe in Go2.
    comment by riobard · 2022-09-16 · in Pingora, the proxy that connects Cloudflare to the Internet
  50. …implement this I would say the maintainer closing the issue, is a pretty clear signal for that: https://github.com/golang/go/issues/48207#event-7373771032
    comment by svnpenn · 2022-09-13 · in Planning Go 1.20 cryptography work