Re: [go-nuts] An old problem: lack of priority select cases

2019-08-29 Thread Robert Engels
My example does have several go routines writing simultaneously. You should read up on how a RWLock works. You can change it to a buffered channel for higher concurrency. The Sleep(1) in the producer is only to add some delay to demonstrate it gets terminated before the desired number of

[go-nuts] liteide x36.1 released

2019-08-29 Thread visualfc
Hi all, liteide x36.1 released, this version folder view support copy and paste, and update gotools and gocode. * LiteIDE Home        http://liteide.org * LiteIDE Source code         https://github.com/visualfc/liteide * Release downloads         

[go-nuts] [ANN] dqlite 1.0.0 - high-availability SQLite

2019-08-29 Thread Free Ekanayaka
Hello, I'd like to announce the release of dqlite 1.0.0 and its associated bindings for Go. Dqlite adds data replication and high-availability to SQLite, using the Raft consensus algorithm. It's perfect for fault-tolerant IoT and Edge devices. See https://dqlite.io/ for more details. Thanks,

[go-nuts] Go 1.13 Release Candidate 2 is released

2019-08-29 Thread Andrew Bonventre
Hello gophers, We have just released go1.13rc2, a release candidate version of Go 1.13. It is cut from release-branch.go1.13 at the revision tagged go1.13rc2. Please try your production load tests and unit tests with the new version. Your help testing these pre-release versions is invaluable.

Re: [go-nuts] An old problem: lack of priority select cases

2019-08-29 Thread T L
On Wednesday, August 28, 2019 at 10:05:06 PM UTC-4, robert engels wrote: > > Here is a version using RWLock https://play.golang.org/p/YOwuYFiqtlf > Doesn't the Read method need to be guarded by the reader lock? > > It won’t run correctly in the playground because it terminates when all >

[go-nuts] Re: Go Module Mirror and Checksum Database officially launched!

2019-08-29 Thread Akram Ahmad
Very cool! This gopher is definitely excited and will be checking out the related blog post soon :) On Thursday, August 29, 2019 at 1:54:15 PM UTC-5, Katie Hockman wrote: > > Hey Gophers! > > We have exciting news to share. Our module mirror > , index

[go-nuts] Go Module Mirror and Checksum Database officially launched!

2019-08-29 Thread Katie Hockman
Hey Gophers! We have exciting news to share. Our module mirror , index , and checksum database are now production ready, and will be on by default for Go 1.13 module users

Re: [go-nuts] An old problem: lack of priority select cases

2019-08-29 Thread Robert Engels
Oops. You are right. The original used two different methods Closed() and Read() and when I refactored I forgot to add the Read lock to the Read(). That's why you always have code reviews...-Original Message- From: T L Sent: Aug 29, 2019 6:25 PM To: golang-nuts Subject: Re: [go-nuts] An

Re: [go-nuts] Help understanding mapping Go<->C structures across IOCTL's

2019-08-29 Thread George Hartzell
Ian Lance Taylor writes: > On Thu, Aug 29, 2019 at 5:15 PM George Hartzell wrote: > > > > Quick summary, I'm trying to understand the Go structures that cgo > > gives me, how they map back onto the C structures and why a Go struct > > that doesn't quite match the cgo output seems to work

Re: [go-nuts] Help understanding mapping Go<->C structures across IOCTL's

2019-08-29 Thread Ian Lance Taylor
On Thu, Aug 29, 2019 at 5:15 PM George Hartzell wrote: > > Quick summary, I'm trying to understand the Go structures that cgo > gives me, how they map back onto the C structures and why a Go struct > that doesn't quite match the cgo output seems to work anyway. > > I've called out two explicit

[go-nuts] Help understanding mapping Go<->C structures across IOCTL's

2019-08-29 Thread George Hartzell
Quick summary, I'm trying to understand the Go structures that cgo gives me, how they map back onto the C structures and why a Go struct that doesn't quite match the cgo output seems to work anyway. I've called out two explicit questions down below. --- The Linux kernel provides a character