[go-nuts] Re: Released sting 1.0.0

Hi Egon Thank you very much for your feedback. You confirmed my assumption about di libraries in go and your links fortified this impression. Probably I have to rethink some old C# habits and map them to a more go idiomatic style. > It's difficult to evaluate the API because the examples

Re: [go-nuts] git submodule vs normal go vendoring

> > If the upstream goes away, you can just re-publish the repo (which you'll > have cloned locally) and adjust the remote URL in .gitmodules. New people > cloning will get the clone from the new source. > Not to counter anything you've said, but dep also allows adjusting the URL.

Re: [go-nuts] git submodule vs normal go vendoring

In theory, the git submodule builds are *more* reproducible, because all your build servers etc have clones of those sub-repos cached under their .git, even though they are not under your control. If the upstream goes away, you can just re-publish the repo (which you'll have cloned locally) and

Re: [go-nuts] Re: How to read multi-page TIFF image?

Nigel, I added the sRGB, cHRM, and gAMA chunks, extended the Encoder structure, and use it like this in my own code: case ".jpg": err = jpeg.Encode(file, p, { Quality: 95, }) if err != nil { log.Fatal(err) } case ".png": // err = png.Encode(file, p) // colorspace and gamma unspecified err =

Re: [go-nuts] Re: Distinct types

On Tue, Oct 3, 2017 at 2:39 PM, xingtao zhao wrote: > var i uint32 = 7 > > > Isn't uint32 an unnamed type? No. It is a named type. It's name is "uint32". Compare to "[]byte", which is an unnamed type literal. Ian -- You received this message because you are

[go-nuts] Re: Distinct types

On Monday, October 2, 2017 at 11:10:58 PM UTC-7, Christian Surlykke wrote: > > Den mandag den 2. oktober 2017 kl. 21.33.04 UTC+2 skrev Dave Cheney: >> >> Back before aliases defined types used to be called named types, which >> permitted the existence of unnamed types. >> >> map[string]string

[go-nuts] Re: Released sting 1.0.0

Hi, I'm going to post few earlier DI discussions and other posts: * https://web.archive.org/web/20140521180901/http://codegangsta.io:80/blog/2014/05/19/my-thoughts-on-martini/ * https://forum.golangbridge.org/t/goldi-lazy-dependency-injection-framework-for-go/1280 *

Re: [go-nuts] Memory issues when spawning 1 million go routines that communicate on a channel

Or you could do it this way... https://play.golang.org/p/rU2ONi51ec On Mon, Oct 2, 2017 at 7:26 PM, Unni Krishnan wrote: > I tried FreeOSMemory, didn't make any difference. > > On Mon, 2 Oct 2017, 5:26 a.m. Ian Lance Taylor, wrote: > >> On Sat, Sep 30, 2017

[go-nuts] Re: goimports build problems "undefined: doTrace"

Ah, thanks I was using build in an attempt to reduce the scope of the problem (under the assumption that one of the things that install did under the hood was call build). (Also it's habit to test things locally before installing them and overwriting the tool I am depending on with a broken

Re: [go-nuts] Go get -f still checking VCS

On 3 Oct 2017, at 10:17, alexandre.ferri...@gmail.com wrote: > > Thanks. However, "go get -t" still complains about "missing Git command". > Indeed, on that machine I intentionally don't use any VCS (just a source > tarball). So I just need the Go compiler to compile and quit trying to brew >

[go-nuts] goimports build problems "undefined: doTrace"

go build works with packages, not files. In this instance you want (from that directory) go build ./goimports May I humbly suggest go install -v, rather than go build. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this

Re: [go-nuts] Go get -f still checking VCS

On Monday, October 2, 2017 at 1:26:31 PM UTC+2, Jakob Borg wrote: > > The documentation for the -f flags says: > > > The -f flag, valid only when -u is set, forces get -u not to verify that > > each package has been checked out from the source control repository > > implied by its import

[go-nuts] Re: Distinct types

Den mandag den 2. oktober 2017 kl. 21.33.04 UTC+2 skrev Dave Cheney: > > Back before aliases defined types used to be called named types, which > permitted the existence of unnamed types. > > map[string]string > > is an unnamed type > > type Dictionary map[string]string > > is a named type, its