Re: [go-nuts] sycall/js : does it require build tags? if so whihc ones?

2021-01-23 Thread Jan Mercl
On Sun, Jan 24, 2021 at 12:57 AM atd...@gmail.com wrote: > My issue is that I do not know which build constraints I should specify for > the static analysers to process the code. Seems like js _and_ wasm: https://golang.org/src/syscall/js/js.go#L5 -- You received this message because you are

[go-nuts] sycall/js : does it require build tags? if so whihc ones?

2021-01-23 Thread atd...@gmail.com
Hello, I'm using atom and am trying to import the syscall/js package. My issue is that I do not know which build constraints I should specify for the static analysers to process the code. I'm getting a message as such: js.go:7:3: build constraints exclude all Go files in /usr/local/go/src/sysca

Re: [go-nuts] possible inconsistency in the embed package documentation

2021-01-23 Thread Manlio Perillo
Il giorno venerdì 22 gennaio 2021 alle 20:02:02 UTC+1 dmit...@golang.org ha scritto: > > Consider the case where example.com/m1/nested is not a separate module. > > Due to the rule of "Patterns must not contain ‘.’ or ‘..’ path > elements", the nested package can not embed, as an example, the LI

Re: [go-nuts] Re: SQLite3 Support without CGo

2021-01-23 Thread Jan Mercl
On Sat, Jan 23, 2021 at 7:02 PM supp...@lieferpool.de wrote: > If you want sqlite3 support without cgo, you might check out > https://github.com/cvilsmeier/sqinn-go Shameless plug: https://pkg.go.dev/modernc.org/sqlite -- You received this message because you are subscribed to the Google Group

[go-nuts] Re: SQLite3 Support without CGo

2021-01-23 Thread supp...@lieferpool.de
If you want sqlite3 support without cgo, you might check out https://github.com/cvilsmeier/sqinn-go s...@infitialis.com schrieb am Dienstag, 13. Dezember 2016 um 14:26:25 UTC+1: > If anyone is interested, I've opened a ticket on GitHub ( > https://github.com/golang/go/issues/18296). > > Please d

[go-nuts] Re: Type-checking from Memory?

2021-01-23 Thread K. Alex Mills
On a second reading, it turns out I do not proof-read all of my emails thoroughly enough before hitting send. My apologies for any confusion and/or alarm. In the meantime, I have solved the problem, so I'm following up here with more context and my solution in case anyone else wants to do somethin