As a way of distributing our go-test run across multiple machines, we are
exploring a client-server architecture. The way we'd like it to work is
that a "go test client" runs on the client machine(s), and repeatedly does
the following:
1) make an http GET request to "http:///more_tests"
You can get and learn on their site (if any) or their repository, for
example :
1. golang dep (https://golang.github.io/dep/)
2. glide (https://glide.sh/)
hope that helps
On Fri, Oct 23, 2020 at 11:57 AM durgasomes...@gmail.com <
durgasomeswararao...@gmail.com> wrote:
> Hi Team,
>
> Anyone help
A concrete example of an "Optional" implementation in present in the sql
package:
https://golang.org/src/database/sql/sql.go?s=4943:5036#L178
In SQL, it's common to have "null" values be distinct from zero values, so
the DB package has a struct with the value and a flag whether the value was
prese
On Fri, Oct 23, 2020 at 12:17 AM Ian Lance Taylor wrote:
> So there are several possible approaches. I'm guessing you want one
> that is more implicit, but as a general guideline Go tends to prefer
> explicit code.
>
>
I don't think there is a good implicit approach to this problem. If you
have
Hi Gerrit,
Yes, that was the plan, but it looks like powerpc support was already added
to the sys/unix package last week.
When we were working on this package we first had several subtle and
difficult to debug problems. As part of debugging, we developed unit tests
for validation of some of the
