[go-nuts] Re: 1.13.4: go mod: weird permissions in pkg/mod after go get

clementauger36 22 nov. 20:35 gow/pkg/mod/ github.com/hashicorp/errwrap@v1.0.0/go.mod -r--r--r-- 1 clementauger clementauger 15977 22 nov. 20:35 gow/pkg/mod/ github.com/hashicorp/errwrap@v1.0.0/LICENSE Le vendredi 22 novembre 2019 20:40:56 UTC+1, clement auger a écrit : > > hi, >

[go-nuts] 1.13.4: x/go/loader: prevent update of the go.mod file ?

hi, I have met another issue with go.mod and x/go/loader. It looks like when it loads, it updates the go.mod in cwd in this example i create a new conf to load tpl package, it results in running the loader in cwd, because I call for Import(), it updates the go.mod and the programmatically import

[go-nuts] 1.13.4: go mod: weird permissions in pkg/mod after go get

hi, I have some weird permissions set on my module files after i run go get on my project. please check my session [clementauger@Host-001 jenjen-stream] $ go version go version go1.13.4 linux/amd64 [clementauger@Host-001 jenjen-stream] $ go env GO111MODULE="" GOARCH="amd64" GOBIN="" GOCACHE="/h

Re: [go-nuts] Re: Package-to-package bindings and package-scope variables

it when I really > understand go.ast and go.parser, the reason being I wanna understand the > most of what is going on under the hood before abstracting it :) > > Le lun. 16 sept. 2019 à 23:10, clement auger > a écrit : > >> hi again, >> >> This looks odd use case

Re: [go-nuts] Re: Package-to-package bindings and package-scope variables

; I saw some //go:linkname pragmas that seem to do what I want but I don't > wanna do things that are not recommended or unsafe, I want to be sure what > I'm doing is the right way to go, or at least that it's not possible with > the current state of the language. > >

[go-nuts] Re: Package-to-package bindings and package-scope variables

hi, it seems you need https://godoc.org/golang.org/x/tools/go/loader https://godoc.org/go/types then select desired package, get its top scope, loop over public names, generate aliases. but i m unsure it is such a good idea to keep those shallow copies around, at least for the case you have f

[go-nuts] Re: Closed channel vs nil channel when writing

sorry i can t find the added value i m looking for within those two publications. thanks for trying to help, it will be good pointers for future readers starting to learn go and reading those words. Le lundi 2 septembre 2019 19:12:03 UTC+2, Jake Montgomery a écrit : > > > On Monday, September

[go-nuts] Re: Closed channel vs nil channel when writing

what the previous content is. > > It's just that Go allows you to receive from a nil variable if that > variable's type is a channel, in which case it blocks forever. > > > > On Sunday, September 1, 2019 at 9:03:58 AM UTC-7, clement auger wrote: >> >

[go-nuts] Closed channel vs nil channel when writing

hi, I am looking for further details and explanations about the various behaviors associated with closed Vs nil channels. I already read https://stackoverflow.com/questions/43616434/closed-channel-vs-nil-channel and other publications such as https://medium.com/justforfunc/why-are-there-nil-ch

Re: [go-nuts] pushing too far reflect usage ? another attempts to pipline based processing

ode gets very ugly. > > Trying to do functional in Go with your proposed syntax would be very > difficult to maintain imo. > > You might find this interesting https://github.com/robpike/filter > > On Aug 6, 2019, at 4:54 PM, clement auger > wrote: > > each tools doe

Re: [go-nuts] pushing too far reflect usage ? another attempts to pipline based processing

Fusco). See if the code is readable by a non > author. > > Generics might improve things here but I doubt it (should help type > safety) I think a lambda syntax is required for trivial transformations in > order to make the streams readable. > > > > On Aug 6, 2019, at 3:

Re: [go-nuts] pushing too far reflect usage ? another attempts to pipline based processing

, Robert Engels a écrit : > > Would honestly want to maintain somebody else’s code that was written in > this style? I wouldn’t. > > On Aug 4, 2019, at 9:13 AM, clement auger > wrote: > > You tell me. > > > https://github.com/clementauger/sta > > > sta - st

[go-nuts] pushing too far reflect usage ? another attempts to pipline based processing

You tell me. https://github.com/clementauger/sta sta - stream async Implements responsive data stream pipeline. It is a reasearch and concept project not to be used in production. Install go get -u github.com/clementauger/sta

[go-nuts] Re: prevent alteration of binaries once distributed in the wild?

thanks to everyone for sharing its thoughts about this question. it confirms what i read elsewhere. this app is to install on the end user computer, and there is no central authority required to use its service.Unlike the game Michael Jones is working on, where somehow the user must to connect s

[go-nuts] prevent alteration of binaries once distributed in the wild?

Hi, I m looking for a technique to prevent binary alteration once distributed in the wild. I have no clue what i m asking for. I was imagining a solution where a signature is prepended to the binary and checked during the startup sequence. However i do understand (well ... i imagine it) the c