Hacker GitHub

← All repos

golang/go

View on GitHub ↗ ★ 139,546 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. OK, another commenter linked to crc32 in the Go standard library: https://github.com/golang/go/tree/master/src/hash/crc32 That has different .s files for different architectures, and a .go file with the platform-independent version, so the…
    comment by iainmerrick · 2017-09-05 · in Go Assembly by Example
  2. …a lower level `go tool` command, of course, but I don't know it off the top of my head. [0]: https://github.com/golang/go/tree/master/src/hash/crc32
    comment by benesch · 2017-09-05 · in Go Assembly by Example
  3. …So yes, I expect it to affect the direction of SmartOS -- and very much for the better! [1] https://github.com/golang/go/issues/20603
    comment by bcantrill · 2017-09-05 · in The sudden death and eternal life of Solaris
  4. Even better is to make a global var sink interface{}, and assign to it. https://github.com/golang/go/issues/14813
  5. …last year[2] by Russ Cox. [1] https://lemire.me/blog/2016/12/21/performance-overhead-when-... [2] https://github.com/golang/go/issues/17373
  6. …that go does use FPATAN on 386 but not Amd64 - found this bug which explains the issues involved: https://github.com/golang/go/issues/17069#issuecomment-24637...
  7. You piqued my curiosity :) A comment in the source for the release notes ( https://github.com/golang/go/blob/master/doc/go1.9.html#L922 ) points to the relevant change: https://go-review.googlesource.com/c/go/+/34310 , which in turn links…
    comment by emfree · 2017-08-25 · in Go 1.9 is released
  8. This is the relevant change: https://github.com/golang/go/commit/0556e26273f704db73df9e7c...
    comment by fmela · 2017-08-25 · in Go 1.9 is released
  9. Thanks and please check this proposal for go2: https://github.com/golang/go/issues/19814 Thumbs up if you like it.
    comment by kokwak · 2017-08-25 · in Go 1.9 is released
  10. Mentions reporting problems with Go on the Experience Reports, probably at this page: https://github.com/golang/go/wiki/ExperienceReports
    comment by kristianp · 2017-08-18 · in The Future of Go
  11. I mean, kinda but not? Based on https://github.com/golang/go/issues/12416 / https://golang.org/cmd/cgo/ : > However, C code may not keep a copy of the Go pointer after the call returns. It looks like they've just punted on the pinning…
  12. node.js: https://github.com/nodejs/node/issues/14644 golang: https://github.com/golang/go/issues/21326 ASP.NET: https://github.com/aspnet/HttpAbstractions/issues/915
  13. …loose. These are the open bugs I'm aware of: https://bugs.openjdk.java.net/browse/JDK-8170568 https://github.com/golang/go/issues/9334
  14. …rules, but nothing earth shattering conceptually. Read up on SSA and study existing code like https://github.com/golang/go/tree/master/src/cmd/compile/int... for real-life optimization. Then there's linker stuff like generating…
    comment by kjksf · 2017-07-28 · in Ask HN: Best book about compilers?
  15. …be hard to tell, which is why they came up with a process and are asking for experience reports: https://github.com/golang/go/wiki/ExperienceReports
    comment by skybrian · 2017-07-22 · in Should Go 2.0 support generics?
  16. …can see what's constant time and what you have to handle yourself to deal with timing attacks in https://github.com/golang/go/commit/850e55b8c028440f2fe28285... The library (as a wrapper) doesn't do anything with regards to timing attacks.
  17. Could that Core Contributor possibly contribute a report to https://github.com/golang/go/wiki/ExperienceReports#generics ? :)
  18. Sounds like https://github.com/golang/go/issues/19335 I guess the performance issue has something to do with some missing optimizations. Hopefully it will get better. Edit: Also https://github.com/golang/go/issues/19361
    comment by e3b0c · 2017-07-14 · in Toward Go 2
  19. …concurrent map type uses interface{} for all keys and values, and therefore offers no type safety: https://github.com/golang/go/blob/master/src/sync/map.go See also: https://github.com/golang/go/issues/18177 All of Go's built-in…
    comment by bascule · 2017-07-14 · in Toward Go 2
  20. …are more containers than that in Go's own standard library : https://golang.org/pkg/container/ , https://github.com/golang/go/issues/18177 > it is possible to build your own, but I think it is not easy enough What does that mean? It is not…
    comment by masklinn · 2017-07-13 · in Toward Go 2
  21. …a `var` in a function body (and also the fact that naked returns are magical in comparison). [1]: https://github.com/golang/go/wiki/CodeReviewComments#named-r...
    comment by cyphar · 2017-06-30 · in Benefits of named return values in Go
  22. https://github.com/golang/go/issues/20859#issuecomment-31220...
    comment by y4m4b4 · 2017-06-30 · in Benefits of named return values in Go
  23. …itself[0] and the Effective Go section on named returns[1] seems positive about their usage. [0] https://github.com/golang/go/blob/master/src/os/file.go (file taken at random) [1] https://golang.org/doc/effective_go.html#named-results…
    comment by laumars · 2017-06-30 · in Benefits of named return values in Go
  24. …adds yet more, but some things are still not pushed down into SSA as well as they could be. (e.g. https://github.com/golang/go/issues/5147#issuecomment-247685... ) Nowadays we can add optimizations much more easily, including writing…
    comment by bradfitz · 2017-06-30 · in Benefits of named return values in Go
  25. I filed a Go bug: https://github.com/golang/go/issues/20859 We should just fix the compiler.
    comment by bradfitz · 2017-06-30 · in Benefits of named return values in Go
  26. Brad Fitzgerald created a github bug to track the issue: https://github.com/golang/go/issues/18892 From what I understand, the WebAssembly team is working on their own GC and the Go team would like to use that rather than rolling their own…
  27. …It can change in future; see https://news.ycombinator.com/item?id=13368846 and even more relevant: https://github.com/golang/go/issues/17271
  28. …sync.Mutex and be done with it. Two lines? I think you underestimate what's going on in sync.Map: https://github.com/golang/go/blob/master/src/sync/map.go
    comment by ngrilly · 2017-06-15 · in Go and Simplicity Debt
  29. …implement these yourself Check the discussion, as usual things aren't as simple as they seem: https://github.com/golang/go/issues/18616
    comment by f2f · 2017-06-15 · in Go 1.9 Beta 1 release notes
  30. It's definitely Minio. :) This kind of worries me though, as Minio is written in Go: https://github.com/golang/go/issues/15658 I've not seen issues with Go on FreeBSD yet personally though, so I'm hoping it's extremely rare. Or that it…
    comment by justinclift · 2017-06-15 · in FreeNAS 11.0 is Now Here
  31. …70 ns to 140 ns on my GCE VM) On Windows, it actually got faster on 64-bit with the addition of: https://github.com/golang/go/commit/e4371fb179ad69cbd057f243... And on macOS, where nobody runs servers, it's basically unchanged speed-wise.
    comment by bradfitz · 2017-06-15 · in Go 1.9 Beta 1 release notes
  32. …concrete benchmarks for different access patterns but I don't see any in the github issue[1]. [1]: https://github.com/golang/go/issues/18177
    comment by helper · 2017-06-15 · in Go 1.9 Beta 1 release notes
  33. …i := range b { b[i] = 0 } } the compiler turns it into a `memclr` call which can be pretty fast: https://github.com/golang/go/commit/f03c9202c43e0abb13066985... Perhaps there could be a performance boost to a simple for-range loop if…
  34. …I don't think it would be possible to write Go's GC in Go unless these special pragmas existed: https://github.com/golang/go/blob/57df2f802f0417f08100ff8002... Also, there are magical variables in the runtime that the compiler knows about…
  35. https://github.com/golang/go/issues/1435 It's not exactly the same issue, but the themes are all the same.
    comment by bboreham · 2017-06-03 · in Linux Namespaces and Go Don't Mix
  36. …and therefore the API is also task-related. Namespaces are not the only problem. See for example https://github.com/golang/go/issues/1435 . The problem is Go runtime does not provide a way to exclusively lock a system thread from existing…
    comment by vbernat · 2017-06-02 · in Linux Namespaces and Go Don't Mix
  37. I was trying to understand the go source code the other day, my process was: `git clone https://github.com/golang/go` then `cd go`, and `tree .`, `git grep ...`, `vim ...`, etc. Anyway, couldn't find how to get the tests to pass, but found…
    comment by dorianm · 2017-06-01 · in Ask HN: Good Go codebases to read?
  38. …main function and tracing through the static structure of the codebase from there: https://sourcegraph.com/github.com/golang/go/-/blob/src/net/... https://sourcegraph.com/github.com/mholt/caddy@master/-/blob...…
    comment by beliu · 2017-06-01 · in Ask HN: Good Go codebases to read?
  39. The standard library source code is pretty good. https://github.com/golang/go
    comment by enahs-sf · 2017-06-01 · in Ask HN: Good Go codebases to read?
  40. …[1] https://pocketgophers.com/go-release-timeline/#go1.8.3 [2] https://github.com/golang/go/issues?q=milestone%3AGo1.8.3
    comment by omginternets · 2017-05-25 · in Go 1.8.3 is released
  41. …be decreasing as the compiler becomes smarter. E.g. instruction reordering is no longer performed ( https://github.com/golang/go/issues/15837 ). You can read about the assemblers here: https://golang.org/doc/asm
    comment by uluyol · 2017-05-25 · in Show HN: C to Go Assembly
  42. …be treated as something to fix, but not something on fire, based on what we currently know. [0] https://github.com/golang/go/issues/20040
    comment by omginternets · 2017-05-24 · in Security fixes released for Go 1.7 and 1.8
  43. There's been some interesting discussion about the possibility of removing them in go 2 https://github.com/golang/go/issues/19921
  44. …map in a sync.RWMutex. Especially considering that sync.Map just uses a mutex under the hood: https://github.com/golang/go/blob/master/src/sync/map.go#L19 edit: although reading the comments, apparently there are conditions where the mutex…
  45. https://github.com/golang/go/issues/19813
  46. …build and no transition performance costs. Although that said you can actually use Go on Android ( https://github.com/golang/go/wiki/Mobile ) but since Go is native code you're stuck with Android's NDK or dealing with JNI and the…
    comment by kllrnohj · 2017-05-17 · in Android now supports Kotlin
  47. …not. From looking at Badger code for example: fd.ReadAt(buf, offset) would block. See this issue: https://github.com/golang/go/issues/6817
  48. …don't understand how to apply basic concepts, or are unaware of other programming languages. [1] https://github.com/golang/go/issues/15292
    comment by grahn · 2017-05-08 · in My Struggles with Rust
  49. It does happen in practice: https://github.com/golang/go/issues/16272
    comment by favorited · 2017-05-01 · in Kotlin doesn’t need an LLVM backend (2016)
  50. Interestingly, the term "reference type" has been removed from the Go spec in 2013: https://github.com/golang/go/commit/b34f0551387fcf043d65cd7d... Yet some semi-official sources (like The Go Programming Language book) do refer to channels…
    comment by eliben · 2017-04-29 · in There is no pass by reference in Go