[go-nuts] [Research Paper] Generic Go to Go: Dictionary-Passing, Monomorphisation, and Hybrid

Researchers from Oxford University (research team lead by Prof. Nobuko Yoshida ) and Pennsylvania State University (research team lead by Prof. Linhai Song ) designed and implemented a dictionary-passing translation for

Re: [go-nuts] Will two Go runtimes in the same process collide over signals/other?

On Mon, Oct 3, 2022 at 9:17 PM Jason E. Aten wrote: > > On Monday, October 3, 2022 at 10:33:42 PM UTC-5 Ian Lance Taylor wrote: >> >> >> > Am I going to get signal handling problems? Is there anything I can do >> > with the signal handling to avoid them? >> >> It's possible. On Linux the dynamic

Re: [go-nuts] What should be in doc.go besides comments and the package?

On Tue, Oct 4, 2022 at 1:27 PM Richard Haven wrote: > > Should one define types in doc.go? The convention is that doc.go only contains a package comment and a package declaration and nothing else. As in fmt/doc.go in the standard library. Of course, this is only a convention. The language

Re: [go-nuts] receiver parameters deserve as good a name as other parameters

All of these are fine opinions to hold. I don't begrudge you them and you can write your code however you prefer. But this is how I would respond if we where working on the same code. On Tue, Oct 4, 2022 at 10:27 PM Richard Haven wrote: > Apart from fulfilling interfaces, function receives are

[go-nuts] receiver parameters deserve as good a name as other parameters

Apart from fulfilling interfaces, function receives are just another parameter, right? "In Go, the receiver of a method is just another parameter and therefore, should be named accordingly" I agree and it inspires me to name receivers well, not to name them more cryptically than other

[go-nuts] What should be in doc.go besides comments and the package?

Should one define types in doc.go? Cheers -- 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

[go-nuts] [security] Go 1.19.2 and Go 1.18.7 are released

Hello gophers, We have just released Go versions 1.19.2 and 1.18.7, minor point releases. These minor releases include 3 security fixes following the security policy : - archive/tar: unbounded memory consumption when reading headers Reader.Read did not

[go-nuts] go-tools

Am I realize correctly, that internal-branch.go1.1x-vendor are these release branches for golang versions(1.16-1.19)? -- 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

Re: [go-nuts] Re: Go implementation of CLP

It would be awesome to help SeaweedFS, so I'm eager to hear more about your ideas to try and understand anything we can do. Sorry if some of my questions are naive. At a high level I'm trying to better understand two topics: 1. the use cases (or features) we/CLP can help with 2. the technical

Re: [go-nuts] Re: Creating and Accessing DLL methods in GO

@squadglad, it is certainly possible to compile go code into a windows DLL, and to use cgo. I've done it successfully. You'll want to study up on cgo. There are strict rules for keeping go pointers and C pointers apart, and they can be subtle. You'll need to be become well versed in the details

Re: [go-nuts] GO API to upload a directory in the github

> undefined: io.Discard What version of Go are you running on your system? io.Discard was introduced in go 1.16 . unsafe.Slice was added in go 1.17 . The most recent version is 1.19, and I'd recommend you use that. On