I think this is brilliant!
Hoping to use it in my next project.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
To view
You can disable this behavior, this link may help:
https://go-review.googlesource.com/c/go/+/21796/
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+u
You may refer to this gist:
https://gist.github.com/nanmu42/90bf2d3870b64aec20b68ec3c104a610
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to g
I don't know you, but to me, writing Golang test is a little dreary.
As a discussion, I think this proposal could bring some improvement.
How do you like it?
https://github.com/golang/go/issues/31135
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" gr
There may be something else in your code that is accidentally wrong.
For debug, try printing time_array in every loop.
I built a similar program for debug, where all seems to be good:
```go
package main
import (
"fmt"
"time"
)
func main() {
var a [32]int
go func() {
time.Sleep(1 * time.Second
Give lower conccurency a try, like 10 requests per second.
If the counter is still keeping up, never down, there may be a real issue.
Handling http request takes time, it is possible that due to slower action of
Mutex, the system has less concurrent load.
--
You received this message because