Re: [go-nuts] Using archive ".a" at time of build

> > Hi Ian, Is there any other way in Go, using which we can hide code of common utilities and still it can be used in different projects (like static and dynamic libraries in C). Rajesh -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To un

Re: [go-nuts] Go if else syntax .. suggested replacement

Dave: Thanks for pursuing this issue and reporting back. Given the extent of responses to the original question by the Go community (pro and con), hopefully those responsible for Go syntax will re-visit the issue and decide whether Go statement "if test then {.. } else { .. }" prevents any po

[go-nuts] Re: WASM persistent storage

As of now, it is open for anybody to investigate and work on it. Until then, calling JS is the best way to go. -Agniva On Monday, 13 May 2019 02:37:16 UTC+2, Luis Furquim wrote: > > Hello Agniva! > > Thanks for the clarification! If I clearly understood the discussion on > that issue, there is

[go-nuts] Re: guarantees on net.Conn and net.UDPConn Read

On Thursday, May 9, 2019 at 2:54:17 AM UTC-4, kortschak wrote: > > The Conn and UDPConn Read methods look like io.Reader Read methods, but > there is no explicit claim that Conn is an io.Reader. Are the Read > methods of these two types identical in behaviour to io.Reader? > I can not say defi

[go-nuts] Passing types that satisfy interfaces - a simple idea ?

(I suspect this is just another "generics" proposal masquerading as something else - but I could find a discussion of this using search) I was wondering about the possibility of passing concrete types to functions as parameters - the onyl requirement being that the concrete type satisfies the i

[go-nuts] Build constraints and preceding non-line comments

Hi Folks, The documentation of build constraints says, in part (emphasis mine): Constraints may appear in any kind of source file (not just Go), but they > must appear near the top of the file, *preceded only by blank lines and > other line comments*. The c

Re: [go-nuts] Build constraints and preceding non-line comments

On Mon, May 13, 2019 at 10:39 AM Neil Schellenberger wrote: > > The documentation of build constraints says, in part (emphasis mine): > >> Constraints may appear in any kind of source file (not just Go), but they >> must appear near the top of the file, preceded only by blank lines and other >>

Re: [go-nuts] Re: WASM persistent storage

Ok! Again, thanks for your attention! On Mon, May 13, 2019 at 12:32 PM Agniva De Sarker < agniva.quicksil...@gmail.com> wrote: > As of now, it is open for anybody to investigate and work on it. Until > then, calling JS is the best way to go. > > -Agniva > > On Monday, 13 May 2019 02:37:16 UTC+2,

[go-nuts] [ANN] Pion WebRTC a Pure Go implementation of the WebRTC API (v2.0.* has stabilized!)

If you are new to WebRTC it is a really amazing technology, and lots of powerful things can be built with it. It isn't just a technology for conferencing, you can build powerful P2P software that works on all platforms (including your browser!) You can see it in use in places like IPFS[0] so co

[go-nuts] bool in go/ast.filterParamList

Hello, While studying the go/ast package, I stumbled upon the following: https://golang.org/src/go/ast/filter.go#L140 Unless I am missing something, shouldnt this just be: https://play.golang.org/p/uQJ3XtEcgWE ? Thanks. -- You received this mess

Re: [go-nuts] bool in go/ast.filterParamList

On Mon, May 13, 2019 at 1:01 PM wrote: > > While studying the go/ast package, I stumbled upon the following: > https://golang.org/src/go/ast/filter.go#L140 > > Unless I am missing something, shouldnt this just be: > https://play.golang.org/p/uQJ3XtEcgWE ? The filterType function is not a pure p

Re: [go-nuts] Re: guarantees on net.Conn and net.UDPConn Read

Thanks, Jake. This was very helpful. On Mon, 2019-05-13 at 09:19 -0700, jake6...@gmail.com wrote: > On Thursday, May 9, 2019 at 2:54:17 AM UTC-4, kortschak wrote: > > > > > > The Conn and UDPConn Read methods look like io.Reader Read methods, > > but  > > there is no explicit claim that Conn is

Re: [go-nuts] Re: guarantees on net.Conn and net.UDPConn Read

On Mon, May 13, 2019 at 2:45 PM Dan Kortschak wrote: > > Thanks, Jake. This was very helpful. It does seem that the docs in this area should be improved. Alas. Ian > On Mon, 2019-05-13 at 09:19 -0700, jake6...@gmail.com wrote: > > On Thursday, May 9, 2019 at 2:54:17 AM UTC-4, kortschak wrote:

Re: [go-nuts] Using archive ".a" at time of build

On Mon, May 13, 2019 at 6:55 AM wrote: > > Is there any other way in Go, using which we can hide code of common > utilities and still it can be used in different projects (like static and > dynamic libraries in C). Not at present. You may want to look at the discussion around https://golang.or

Re: [go-nuts] Re: guarantees on net.Conn and net.UDPConn Read

Yes. There's also the unfortunate collision with io.ReaderFrom's method name which is directionally opposite to net.PacketConn's ReadFrom. This is unfixable because of Go1. Dan On Mon, 2019-05-13 at 15:14 -0700, Ian Lance Taylor wrote: > On Mon, May 13, 2019 at 2:45 PM Dan Kortschak > wrote: > >

Re: [go-nuts] go runtime in DLL not getting intialized(?) on some windows hosts

Installing the Go build environment locally on the deploy host fixed the crash. I'm guessing it is probably the missing timezone data on Windows, as in https://github.com/golang/go/issues/21881 or some other assumption by the runtime inside the DLL that it is running on a machine that has the

Re: [go-nuts] go runtime in DLL not getting intialized(?) on some windows hosts

Indeed, confirming data: I can re-create the crashing circumstances immediately by renaming C:\Go to C:\Go1.12.5. On Tuesday, May 14, 2019 at 3:53:10 AM UTC+2, Jason E. Aten wrote: > > Installing the Go build environment locally on the deploy host fixed the > crash. I'm guessing it is probably t

Re: [go-nuts] go runtime in DLL not getting intialized(?) on some windows hosts

file an issue, please, if you have not done so already. i'd like to follow it. On Mon, May 13, 2019 at 8:01 PM Jason E. Aten wrote: > > Indeed, confirming data: I can re-create the crashing circumstances > immediately by renaming C:\Go to C:\Go1.12.5. > > On Tuesday, May 14, 2019 at 3:53:10 AM U

Re: [go-nuts] go runtime in DLL not getting intialized(?) on some windows hosts

Further confirmation: with the env var GOROOT set to C:\Go, it is sufficient to have exactly one file under then entire C:\Go directory tree: C:\Go\lib\time\zoneinfo.zip alone allows the Go runtime to start cleanly inside the DLL. The zoneinfo.zip file allows the runtime to start. We should re

Re: [go-nuts] go runtime in DLL not getting intialized(?) on some windows hosts

andrey: voice your support on https://github.com/golang/go/issues/21881 It's been a known issue since 2017 and really needs to be fixed. On Tuesday, May 14, 2019 at 4:05:55 AM UTC+2, andrey mirtchovski wrote: > > file an issue, please, if you have not done so already. i'd like to follow > it.

[go-nuts] Re: Passing types that satisfy interfaces - a simple idea ?

You mean something like this ? Henry On Tuesday, May 14, 2019 at 12:40:01 AM UTC+7, x...@gmail.com wrote: > > (I suspect this is just another "generics" proposal masquerading as > something else - but I could find a discussion of this using search) > >

Re: [go-nuts] bool in go/ast.filterParamList

Got it, thank you. -- 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...@googlegroups.com. To view this discussion on the web visit https://gro