I saw an old discussion about this (and it might have a solution too)
https://github.com/golang/go/issues/16652
Op maandag 8 augustus 2022 om 17:12:11 UTC+2 schreef mandel...@gmail.com:
> There should be a way to access the full information a driver has for
> result columns.
>
--
You received
I am sure that many of us have been on that journey. After using Go for
some time, we discover some practices that are not necessarily in agreement
with the existing "adages" but effectively solve our problems.
For me, if the data type is mutable, I prefer returning interfaces. It
would be so
So it seems that reentrant locks are a hard requirement after all.
The reason being that an event handler can itself trigger an event which
will be handled by a similar callback synchronously. (basically, callback
composition)
If the first event handler locks the UI tree, the next synchronous cal
On Mon, Aug 8, 2022 at 4:51 AM Volker Dobler wrote:
>
> Executing code during build is a 100% no-go from a security perspective.
> Especially arbitrary 3rd party code.
>
> So let me rephrase it:
>
> > One of the big advantages of Go's build systems is that running
> > generators is **not** automat
I can't speak to the *auto-generated swagger client* case but I believe
gRPC is still doing things the right way -- in that the framework defines
an interface I (the framework API consumer) then implements. IOW: I don't
see that as a "java style interface" (where the interface defines the API
On Mon, Aug 8, 2022 at 12:51 PM Tim Peoples wrote:
> I don't necessarily consider the "multiple implementations" case as being
> truly preemptive -- if there really are multiple implementations (e.g. the
> "hash" package from the standard library).
>
> I'm much more concerned about interfaces tha
I don't necessarily consider the "multiple implementations" case as being
truly preemptive -- if there really are multiple implementations (e.g. the
"hash" package from the standard library).
I'm much more concerned about interfaces that are defined by an API
producer -- for one and only one im
On Mon, Aug 8, 2022 at 11:17 AM Tim Peoples wrote:
>
> For years I've read the old adage, "Accept interfaces, return structs" and
> have spent years working to instill this understanding among my colleagues.
> I gathered a great many skills while learning Go (and acquiring
> readability) back in
For years I've read the old adage, "Accept interfaces, return structs" and
have spent years working to instill this understanding among my colleagues.
I gathered a great many skills while learning Go (and acquiring
readability) back in the day -- and one of the strongest of those is the
idea
There should be a way to access the full information a driver has for
result columns.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@goo
Executing code during build is a 100% no-go from a security perspective.
Especially arbitrary 3rd party code.
So let me rephrase it:
> One of the big advantages of Go's build systems is that running
> generators is **not** automated.
V
On Monday, 8 August 2022 at 12:34:43 UTC+2 stalke...@proton
One of the big advantages of many other build systems and for which reason
many Go projects use Makefiles is that running generators is not automated.
As I see it, the only thing required to make it automatic is annotation to
make note of the sources that generators build off and trigger rerunni
Put `func use(...interface{}) {}` into any *_test.go file.
Call it with any variable(s) that is/are temporarily unused during
testing/debugging. It work also for unused imports by naming something from
the package.
The code does not compile outside of `$ go test`, it's not possible to
forget and
This is horrible.
The 'declared but not used' error saved me hundreds of times,
and for experimenting, adding a "_ = notUsed" or hide the whole part behind
an "if false" is not a burden.
george...@gmail.com a következőt írta (2022. augusztus 6., szombat,
16:26:33 UTC+2):
> Hi everyone!
>
> I
14 matches
Mail list logo
