Re: [go-nuts] Re: An mistake in tip spec?

2022-01-07 Thread 'Robert Griesemer' via golang-nuts
Indeed. There's no shortcuts possible here. Hopefully this works better (and closely matches the implementation): https://go-review.googlesource.com/c/go/+/376834 - gri On Thu, Jan 6, 2022 at 10:08 PM Axel Wagner wrote: > On Fri, Jan 7, 2022 at 2:35 AM 'gri' via golang-nuts < > golang-nuts@googl

[go-nuts] Re: Command `go test` without build constraints does not work

2022-01-07 Thread 'Bryan C. Mills' via golang-nuts
I think the distinction between "unit" and "integration" tests may be a red herring. As a user running tests, generally I want to be able to run “fast” or “smoke” tests (for quick iteration) vs. “slow” or “intensive” tests (to check for regressions and larger-scale statistical properties, and pe

Re: [go-nuts] Go 1.18 beta Feedback & Questions

2022-01-07 Thread Ian Lance Taylor
On Fri, Jan 7, 2022 at 3:54 AM Joa Ebert wrote: > > I thought I provide some "realworld" feedback for the Go 1.18 beta and > generics. > > I recently spend some time implementing a concurrency framework that mimics > Scala's Futures and Promises API in Go as a learning exercise. > > You can find

[go-nuts] TiExec: Try to Bring Direct Performance Improvement to Go Applications by Alleviating iTLB-Cache-Miss

2022-01-07 Thread hnes
TiExec tries to alleviate the iTLB-Cache-Miss of the application it loaded, so it may bring some direct performance improvement to those applications that are being punished by iTLB-Cache-Miss problem. I guess many Golang applications which have a large .text segment might already suffer from t

[go-nuts] Go 1.18 beta Feedback & Questions

2022-01-07 Thread Joa Ebert
Hey, I thought I provide some "realworld" feedback for the Go 1.18 beta and generics. I recently spend some time implementing a concurrency framework that mimics Scala's Futures and Promises API in Go as a learning exercise. You can f

[go-nuts] Re: Need some advice on multiple sockets and goroutines

2022-01-07 Thread Brian Candler
I don't think there's a hard-and-fast answer here. You can pass pointers to objects to avoid copying, so it's really a question of how you synchronize the per-socket goroutines with the summarising goroutine. I can think of different ways of doing this depending on the exact requirements. One