Re: [go-nuts] about -buildmode c-shared

2021-02-13 Thread Frédéric De Jaeger
On Tuesday, February 9, 2021 at 2:46:33 AM UTC+1 Ian Lance Taylor wrote: > > > Thanks, you may be correct: it may be possible to hide all symbols > other than the ones that are intended to be exported to the C program. > If it is possible to do that reliably in all cases, then the effect > sh

Re: [go-nuts] about -buildmode c-shared

2021-02-13 Thread Ian Lance Taylor
On Sat, Feb 13, 2021 at 1:53 AM Frédéric De Jaeger wrote: > > On Tuesday, February 9, 2021 at 2:46:33 AM UTC+1 Ian Lance Taylor wrote: >> >> >> >> Thanks, you may be correct: it may be possible to hide all symbols >> other than the ones that are intended to be exported to the C program. >> If it i

[go-nuts] How to get VSCode to use different Go env vars for different directories in the same repo?

2021-02-13 Thread Michael Ellis
*(Sorry for posting what is mostly a VSCode question. I've asked it on StackOverflow without getting any responses. Am reposting here in the hope that some has already run into this problem and figured out how to deal with it.)* I have a Go project that builds a WebAssembly (WASM) app and a b

[go-nuts] Re: How to get VSCode to use different Go env vars for different directories in the same repo?

2021-02-13 Thread Alex
Try setting ""go.testEnvVars"" and "go.toolsEnvVars" On Sunday, 14 February 2021 at 4:42:06 am UTC+8 michael...@gmail.com wrote: > *(Sorry for posting what is mostly a VSCode question. I've asked it on > StackOverflow without getting any responses. Am reposting here in the hope > that some has

[go-nuts] Error handling

2021-02-13 Thread Michael MacInnis
I've been playing around with reducing error handling boilerplate using standard language constructs. I'm currently doing something that looks like this: import ( "github.com/michaelmacinnis/handle" ) func do(name string) (err error) { check, handle := handle.Err