golang-nuts@googlegroups.com

Anyone familiar with C/C++ will be familiar with the current convention of using an asterisk to indicate a pointer to the value. Yes, there is a reasonable argument for using an ampersand but either syntax is essentially arbitrary; thus a coin flip as to which to use. So we might as well use the C

golang-nuts@googlegroups.com

On Tue, Mar 5, 2024, 8:33 PM Matheus Fassis Corocher < matheuscoroc...@gmail.com> wrote: > I was studying about pointers and struct in Golang and one thing that I > don't understand is why using * in return of signature of function instead > of & if the return of function is an address of variable

golang-nuts@googlegroups.com

I was studying about pointers and struct in Golang and one thing that I don't understand is why using * in return of signature of function instead of & if the return of function is an address of variable? The correct version that works: func NewVertex(X, Y int) **Vertex* { ... return &Verte

Re: [go-nuts] Loop unit char entered

Daniel, I'd like to see source code for this if you're able. Thanks, Mike On Saturday, April 16, 2022 at 6:21:30 AM UTC-4 Daniel Jankins wrote: > Thank you, > That is what I did. It works very well. > Thank you again > > On Fri, Apr 15, 2022 at 8:48 PM Kurtis Rader wrote: > >> On Fri, Apr 15,

[go-nuts] [security] Go 1.22.1 and Go 1.21.8 are released

Hello gophers, We have just released Go versions 1.22.1 and 1.21.8, minor point releases. These minor releases include 5 security fixes following the security policy : - crypto/x509: Verify panics on certificates with an unknown public key algorithm Veri

Re: [go-nuts] GO111MODULE=off go get deprecated?

On Mon, Mar 4, 2024 at 8:52 PM Jeffery Carr wrote: > On Monday, March 4, 2024 at 8:44:14 AM UTC-6 Bryan C. Mills wrote: > > Per https://go.dev/doc/go1.22#go-command: > > go get is no longer supported outside of a module in the legacy GOPATH mode > (that is, with GO111MODULE=off). Other build comm

[go-nuts] Re: c-shared library for Aix

I tried with clang also but not luck, tried different approaches like using gccgo to directly build c-shared vs building c-archive using golang and then converting it to c-shared by linking using gcc/clang. No luck at all. On Sunday 3 March 2024 at 20:29:12 UTC+5:30 TheDiveO wrote: > llvm/clang