[go-nuts] How to prevent net/http from canonicalizing request paths?

explicitly register a handler for each possible path where this problem exists under /foo. -- Benoit "tsuna" Sigoure -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails fr

Re: [go-nuts] 2.5x higher memory usage with go1.8rc2

ate on this? I'm curious. > > > > > Aurélien Bombo > > 2017-01-24 23:20 GMT+01:00 tsuna : >> >> Hi there, >> I have a linux/386 production binary that I compiled and deployed with >> go1.8rc2 and I noticed that the RSS is 2.5x of the same binary doing

[go-nuts] 2.5x higher memory usage with go1.8rc2

(admittedly some time ago) I couldn’t find an updated tool that groked heapdump15. -- Benoit "tsuna" Sigoure -- 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 e

Re: [go-nuts] Re: Efficient ForEach() on a map protected by a mutex

to the insane memory overhead. So the absence of complaints from the race detector is a good thing, and we already run our unit tests with it in an automated fashion, but that’s no substitute for actually looking at the logic in the code and asking the question “is this actually legit”. -- Benoit

Re: [go-nuts] Re: Efficient ForEach() on a map protected by a mutex

On Sat, Jan 7, 2017 at 7:00 PM, 'Keith Randall' via golang-nuts < golang-nuts@googlegroups.com> wrote: > > > On Friday, January 6, 2017 at 5:12:54 PM UTC-8, tsuna wrote: >> >> Hi there, >> I have a struct that contains an unexported map protec

[go-nuts] Efficient ForEach() on a map protected by a mutex

insertions in mind, is this implementation of ForEach correct? Is there a better way? Thanks. -- Benoit "tsuna" Sigoure -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails

Re: [go-nuts] Compiler level memory barrier in Go i.e. asm volatile("" : : : "memory")

this then it wouldn’t >> confuse so many users and even Go developers? >> >> >> >> John >> >> John Souvestre - New Orleans LA >> >> >> >> From: Rob Pike [mailto:r...@golang.org] >> Sent: 2015 February 08, Sun 00:05 >>