I agree. That is what I settled on, basically. Thanks for the suggestion!
Will
On Fri, Dec 23, 2022 at 10:23 AM Brian Candler wrote:
>
> I don't know how a raw Go interface value would be usable in Javascript. As
> an alternative, would it be any good to use sprintf("%T", readErr) as the
> co
I don't know how a raw Go interface value would be usable in Javascript.
As an alternative, would it be any good to use sprintf("%T", readErr) as
the code, and readErr.Error() as the value? At least those are both strings.
https://go.dev/play/p/nd1FXUvD_zg
On Friday, 23 December 2022 at 14:33:
Hello everyone!
First, thank you *all* (I mean this great community) for the Go language
and especially its support for a wasm target.
As I was attempting to finish up a CL
(https://go-review.googlesource.com/c/go/+/458395) I found occasion to need
to great a JS Error based on a Go error. I w
I've made Windows DLLs work with Go, so I can be done, but I would
strongly suggest that you avoid it. Windows applications expect to be
able to unload their DLLs, and you can never do that with Go.
There are work arounds, (search this form for my previous posts),
but they are ugly and fragile.
So
Testing style will tend to be shaped by both personal preference and the
needs of the project.
Personally, I do a ton of data-driven tests, as is required by my
data intensive projects (custom databases; analytics on them).
I often use a fork of goconvey for my testing. It promotes BDD
style
Hallöchen!
'Robert Findley' via golang-nuts writes:
> You can disable the "composites" analyzer: https://github.com/golang/
> tools/blob/master/gopls/doc/analyzers.md#composites
>
> Update the "analyses" configuration to include "composites": false,
> as described here: https://github.com/golang/
