Re: [go-nuts] Re: Go 1.9.3 is released

Thanks for the heads up. I corrected the issue. On Mon, Jan 22, 2018 at 11:08 PM Ian Lance Taylor wrote: > [ +andybons ] > > On Mon, Jan 22, 2018 at 6:10 PM, wrote: > > Hi Go team, > > > > It seems that the go1.9.3 tag is not on the good commit,,

Re: [go-nuts] Re: Go 1.9.3 is released

[ +andybons ] On Mon, Jan 22, 2018 at 6:10 PM, wrote: > Hi Go team, > > It seems that the go1.9.3 tag is not on the good commit,, it's not possible > to do `git checkout go1.9.3`. > > - current go1.9.3 tag: >

Re: [go-nuts] Re: Experience Report building OCR in Go

Thanks for your informative report. I fully agree with you re the zero value of maps. A read-only empty is useless. -- 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

Re: [go-nuts] Re: JSON and Embedded Types (Aliases)

I think have misspoken. Even though the field's name appears exported via reflection (it has a name that starts with a capital letter), attempting to use the reflect.Value's SetInt method panics, indicating that the field was obtained using an unexported field. So the encoding/json package is thus

Re: [go-nuts] Re: JSON and Embedded Types (Aliases)

The discordance is unexpected. On Mon, 2018-01-22 at 19:28 -0500, Josh Humphries wrote: > I think that is expected, and it is the JSON marshaling that is > surprising > (and erroneous). > > If it were expected that the embed field names resolved to the alias > *target > type* name, it would

Re: [go-nuts] Re: JSON and Embedded Types (Aliases)

I think that is expected, and it is the JSON marshaling that is surprising (and erroneous). If it were expected that the embed field names resolved to the alias *target type* name, it would instead be a compiler error since the compiler does not allow embedded types that would result in name

Re: [go-nuts] Re: JSON and Embedded Types (Aliases)

This is sort of surprising though: https://play.golang.org/p/mjfkzIqAo_b On Mon, 2018-01-22 at 10:20 -0800, C Banning wrote: > From the Language Specification -  > > A field declared with a type but no explicit field name is called an > *embedded  > field*. An embedded field must be specified as

Re: [go-nuts] What is go concurrency based on?

The references in the Wikipedia article have a lot of overview detail: https://en.wikipedia.org/wiki/Go_(programming_language)#Concurrency:_goroutines_and_channels I’m not convinced Node.js or Go are inherently more efficient than multithreading. Due to the overhead of repeating operating

[go-nuts] Go 1.9.3 is released

Hi gophers, We have just released Go version 1.9.3, a minor point release. This release includes fixes to the compiler, runtime, and the database/sql, math/big, net/http, and net/url packages. View the release notes for more information:

Re: [go-nuts] What is go concurrency based on?

The ultra-short and precise answer to this question is: multithreading. Go implements a multithreaded runtime which maps goroutines to threads in an N:M style. The idea is to obtain the efficiency of a libev model without limiting yourself to a single core. The hard part is to manage the mapping

[go-nuts] What is go concurrency based on?

Hi, I'd like to know what go concurrency is based on. For example, nodejs is based on libev, making nodejs more efficient than using multithreading to handle concurrency. What is go based on to make go concurrency more effecient than multithreading? -- Regards, Peng -- You received this message

[go-nuts] Re: Badger Write Performance

I've followed badger since it's beta and the discussions it emitted. Those "lines" and discussions, alongside it's history, do not provide the most happy influence that one would hope for. On Sunday, January 21, 2018 at 7:51:52 PM UTC+3:30, Diego Medina wrote: > > The use of SyncWrites=false on

Re: [go-nuts] Re: JSON and Embedded Types (Aliases)

>From the Language Specification - A field declared with a type but no explicit field name is called an *embedded field*. An embedded field must be specified as a type name T or as a pointer to a non-interface type name *T, and T itself may not be a pointer type. The unqualified type name

Re: [go-nuts] Re: Go schedule latency issue

Beware of running the test generator on the same machine as the SUT (system under test). There are several things here: * On localhost, the network stack bypasses several kernel parts. This may lead to wrong test data. * The test generator might steal resources from the SUT, skewing the numbers

[go-nuts] Re: How to convert a xml content to map[string]interface?

Your lib works great and proves that actually there is a way to decode an XML stream into a generic map avoiding the need to declare the data model. (for the ones who know Perl is kinda XML::Simple...) Thanks! Il giorno venerdì 6 novembre 2015 13:31:55 UTC, C Banning ha scritto: > > What's

Re: [go-nuts] Re: JSON and Embedded Types (Aliases)

You are right, I am wrong. I wasn't aware that the struct field would be named after the alias, I assumed it would be named after the type itself. I agree that this looks like a bug in the json-package and that it should look at the field name itself. On Mon, Jan 22, 2018 at 4:47 PM, Josh

[go-nuts] Re: resource cleanup in closure

I assume you know where your interface{} will no longer be used. Why not put in an explicit optimization structure delete there? There's already a New, make a Done or something like that. Matt On Sunday, January 21, 2018 at 6:41:00 PM UTC-6, simon place wrote: > > after a bit of thought, its

Re: [go-nuts] Re: JSON and Embedded Types (Aliases)

I'm not trying to suggest that the example code makes sense or is something that one *should* do. But it is surprising behavior that is not expected, even after reading relevant parts of the language spec and the reflect and json package docs. It looks like this is a bug in the json package.

[go-nuts] Re: Go schedule latency issue

The higher priority -19 we're interested in has the Permission denied error message, the command needs to be run with elevated OS privileges. Is waf-client the program that has the real-time requirement? If you separate the calling process out to a separate computer do you still see the delay?

Re: [go-nuts] Re: JSON and Embedded Types (Aliases)

On Mon, Jan 22, 2018 at 8:50 AM, dc0d wrote: > Then the main question would be why is it possible to embed type aliases? > Because it is possible to embed types and an alias is simply another name for a type. For example, embedding an x/image/draw.Image