[go-nuts] Re: Unexpected lack of parallel speedup

I don't have specific answers, but I do have some thoughts. First, the externally parallel has no overhead related to coordination. I would expect you to get the result you have of full core utilization and nearly perfect scaling. As soon as you have a common resource, you will have the

Re: [go-nuts] How to deal with "Expect: 100-continue" *without* sending a 100 status

Sorry to resurrect a month old thread, but I just implemented bullet #2 with this patch. I need to disable the automatic 100-continue behavior so that my handler can reply with a 40X status before the client read the 100-contine and starts sending data. On Saturday, September 17, 2016 at

Re: [go-nuts] Re: Working with "characters" in strings

Please read blog.golang.org/strings. -rob On Sat, Oct 29, 2016 at 12:08 PM, wrote: > thanks! whats the "a:b" in this instance? did you mean s[i:i+1]? wouldn't > that return a slice? > > so when iterating I'm comparing/using runes but what is the best way to > refer to the

[go-nuts] Unexpected lack of parallel speedup

I'm trying to parse OpenPGP key server dumps. Throughput is not too bad so far, but I'd like to speed things up by introducing parallelism. The dumps are split into several files (each about 40 MB large, with a few thousand keys). The toy version I have so far does not need any coordination

[go-nuts] golang.org/x/crypto/openpgp RSA public exponent size limit

PublicKey.parseRSA() has this check: if len(pk.e.bytes) > 3 { err = errors.UnsupportedError("large public exponent") return } I get that it is valuable to limit the exponent size, but this limit is too low: quite a few RSA keys in a dump from the

[go-nuts] Re: [golang-dev] Re: Stalking people online for thought crimes! This is what the Go project has succumbed to!

+golang-nuts bcc golang-dev On Fri, Oct 28, 2016 at 11:26 PM wrote: > If you don't like the framework just don't use it. > I'm using this framework in production for a long time and the author > makes his best to solve any incoming issue. > > He, literally, gave his

[go-nuts] Global logger not concurrent safe ?

First try to run with the race detector - compile with "-race" flag, and fix EVERY race! You may coordinate the mutators and readers by using channels or mutexes. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group

[go-nuts] Global logger not concurrent safe ?

First try to run with the race detector - compile with "-race" flag, and fix EVERY race! You may coordinate the mutators and readers by using channels or mutexes. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group

[go-nuts] Re: CGO: How to link static library across dependent packages?

Hi Mate, why Don't you try to make a static binary go build --ldflags ' -extldflags "-static"' filename.go On Thursday, October 27, 2016 at 8:10:55 PM UTC+5:30, pat.s...@gmail.com wrote: > > Folks, > > Two of my packages have dependency on the same C library. I have linked > them

Re: [go-nuts] Logging concurrent safe ?

On 2016-10-29 13:37, Łukasz Kostka wrote: Hi. In docs I can see that logger can be safely used in multiple coroutines. I've implemented this, but my program seems to freeze at random. Am I

[go-nuts] [ANN]: httptp - http(s) proxy and load balancer that saves network bandwidth

Hi all, I'd like to announce httptp - http(s) proxy and load balancer that saves network bandwidth. It is built on top of httpteleport package . Any highly loaded http-based API service

Re: [go-nuts] CGO: How to link static library across dependent packages?

On Fri, Oct 28, 2016 at 9:36 PM, wrote: > >>go build > # agent > //goLang/go/pkg/tool/linux_amd64/link: running gcc failed: exit status > 1 > //tmp/go-link-022070709/01.o: In function `putStringToBuffer': > //goLang/goCode/src/eventbridge/EventBridge.c:31: multiple

[go-nuts] Global logger not concurrent safe ?

Hi. I'd like to have some easy logging/debugging mechanism for my program . In log documentation I can see that logger is guaranteed to be thread safe and can be used in multiple goroutines.

[go-nuts] Working with "characters" in strings

I know that strings are an immutable sequence of bytes, so what would be the most idiomatic way to handle the following operations. - Convert a string to []string (slice) or [n]string (array). Eg. "foobar" to ["f" "o" "o" "b" "a" "r"] - Iterate through a string and evaluate the

[go-nuts] Working with characters in strings

I understand that strings are immutable sequences of bytes and wanted to know how to idiomatically work with the "characters" within a string. For example how should I approach the following operations - Convert a string to a []string (slice or array). eg. "foobar" to ["f" "o" "o" "b"

[go-nuts] Logging concurrent safe ?

Hi. In docs I can see that logger can be safely used in multiple coroutines. I've implemented this, but my program seems to freeze at random. Am I doing something wrong ? -- You received

Re: [go-nuts] Re: Stalking people online for thought crimes! This is what the Go project has succumbed to!

I don't like CoC. But I like wise moderation. I may to be toxic sometimes. I think, it is inevitable human nature (although some tries to look like sweet candies). But I don't want to be extremly toxic. I do not want to offend without reason. I've been contacted privately by Andrew Gerrand two