Re: [go-nuts] Re: Struggling with go mod, micro-repos and private forks

On Friday, October 25, 2019 at 10:19:03 AM UTC-4, Shaun Crampton wrote: > > > > We have https://golang.org/issue/26232 open for 2FA workflows in general. >> >> In the meantime, you may need to configure a Personal Access Token >>

[go-nuts] module dependency & testing

A dependency is a dependency. There are no scopes like you might find in Maven(Java) land. Your project needs these "test deps" to run your tests, so they are in your module file. Even so, Go is smart enough when it builds your binary to not include the extra bloat. -- You received this

Re: [go-nuts] Re: GO Mod (modules) for dummies. Please help.

Don’t be frustrated. The design could be better imo. I am assuming much of the complexity comes from trying to optimize the build across projects that share common modules. I think there are easier ways to accomplish this. Simple mappings to version labels would be easier imo. > On Oct 25,

Re: [go-nuts] Re: Struggling with go mod, micro-repos and private forks

We have https://golang.org/issue/26232 open for 2FA workflows in general. > > In the meantime, you may need to configure a Personal Access Token > > to > get HTTPS to work. >

[go-nuts] Re: GO Mod (modules) for dummies. Please help.

Well I can see that I am not getting this. I will carry on coding and see if the understanding I have resolves itself. Thanks for all you contributions. On Monday, 23 September 2019 16:25:30 UTC+1, Stuart Davies wrote: > > Hi. > > > I have been using GO for about a year and I love the language

Re: [go-nuts] How to build gollvm on arm platform

> > The way that I had imagined this working was that either each > testpoint has a loop over the various supported ABI flavors (and checks > output for each flavor) > Yes, for those common test cases, I just did this. > or we have separate testpoints for each ABI > (e.g.

Re: [go-nuts] How to build gollvm on arm platform

Hi Eric, Yes, this is a problem that is pretty much guaranteed to happen given the way the C ABI works in LLVM. All of the test results in BackendCABIOracleTests.cpp are specific to the details of the amd64 ABI. The way that I had imagined this working was that either each testpoint has a loop

Re: [go-nuts] How to build gollvm on arm platform

Hi Than, I'm porting the unit test cases of x86 to arm64. As the difference between x86 abi and arm64 abi, for the same go code snippet, the generated llvm IRs maybe different. How do you get the correct IR result of a unit test? Such as unit test TEST(BackendCABIOracleTests, RecursiveCall1).

[go-nuts] module dependency & testing

Hi, Say you have a project with: - hard dependencies - some extra dependencies only used during testing, not needed otherwise Are they treated equally? When you switch to go modules, does the second group become hard dependencies? It seems like they do. -- You received this message because