Re: [go-nuts] [gollvm] Cannot build project : no type named 'CompositeType' in namespace 'llvm'

Hi, It seems to be building fine now. Thank you for your fast reply ! Le mardi 31 mars 2020 21:04:52 UTC+2, Than McIntosh a écrit : > > CL submitted. If you can please update your client and try your build > again, it should go through. > > Thanks, Than > > On Tue, Mar 31, 2020 at 2:56 PM Than

[go-nuts] Re: Using modules with private repos

I have become totally confused about using local modules. Please help -- I'll try to keep this short: I have a package (dfs) and a main package. I tried laying things out an using _ for local packages from your excellent post on github, but I still cannot get things to build correctly. I got the

[go-nuts] Pseudo version showing different in go1.12 and go1.13

Hi, I created go.mod file from two different go versions 1.12 and 1.13: module /home/nsaboo/project go 1.13 require ( github.com/aws/aws-sdk-go v1.8.3-0.20170325041625-2150862edc16 github.com/go-ini/ini v1.55.0 // indirect github.com/jmespath/go-jmespath v0.3.0 // indirect githu

[go-nuts] Re: Using modules with private repos

With all the examples out there and a little experimentation, I found the solution I needed. Here's the tree from the 'top' directory: ├── dfs │ ├── dfs.go │ ├── dfs_test.go │ └── go.mod ├── first.go ├── go.mod └── ModuleDFS Here are the file contents starting from the top of the directory s

Re: [go-nuts] go1.14/go1.14.1 missing some debug information

Thanks for filing the issue (https://github.com/golang/go/issues/38192). I added some comments. On Wed, Apr 1, 2020 at 12:46 AM Ian Lance Taylor wrote: > On Tue, Mar 31, 2020 at 5:19 PM sanye wrote: > > > > Hello gophers, > > I have a problem when debugging with gdb using go1.14/1.14.1, set a

[go-nuts] Code generation with LLVM bindings

It isn't immediately obvious to me which package should be used to generate code using LLVM and go bindings. On the one hand there is this package: https://godoc.org/llvm.org/llvm/bindings/go/llvm But I also see this one: https://github.com/llir/llvm Which seems to be specifically about IR.

Re: [go-nuts] Re: Using modules with private repos

This is actually a fairly neat solution! I might look at using that from here on out. How well does it work if something else (also with access to your private repository) tries to include your module? - Dave > On Apr 1, 2020, at 11:47 AM, Dave Mazzoni wrote: > > With all the examples out

[go-nuts] Timer.Reset() (again...)

Hi Folks, I am almost certainly overthinking this or in some other way "doing it wrong"--so please (dis)abuse me. The Timer.Reset() documentation reads (in part) "Reset should be invoked only on stopped or expired timers with drained channels." Am I correct in understanding that "should" in th

[go-nuts] Re: HSV image format

On Sunday, March 29, 2020 at 11:30:02 AM UTC-6, Scott Pakin wrote: > > Does anyone know of a package that provides an image.Image > with an HSV color model > ? I've found lots of > functions that convert color mode

Re: [go-nuts] Timer.Reset() (again...)

On Wed, Apr 1, 2020 at 11:05 AM Neil Schellenberger wrote: > > I am almost certainly overthinking this or in some other way "doing it > wrong"--so please (dis)abuse me. > > The Timer.Reset() documentation reads (in part) "Reset should be invoked only > on stopped or expired timers with drained c

Re: [go-nuts] Timer.Reset() (again...)

Thank you very much for confirming that, Ian! FWIW the scenario is very roughly along the lines of a "best effort re-configurable" timeout for a work loop: timeout := <-timeoutConfigC timer := time.NewTimer(timeout) defer timer.Stop() for { select { case timeout = <-timeoutConfigC: t

Re: [go-nuts] Recommended way to prevent my project being built with an old Go version?

Thanks Ian for the fast and authoritative answer. I'll do what you suggest. Cheers, Tom On Tuesday, March 31, 2020 at 2:31:19 AM UTC+1, Ian Lance Taylor wrote: > > On Mon, Mar 30, 2020 at 6:22 PM Tom Payne > > wrote: > > > > Go's backwards compatibility guarantee is fantastic, but only applies