[go-nuts] Re: Migrating to modules

Thanks Kasun, One thing that is not 100% clear is what packages and versions (more importantly) get set when you migrate to using modules. Is it the current version on the local disks? Lee -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To un

[go-nuts] Re: Migrating to modules

According to this it will try to create an equivalent build. It will not break your code On Thursday, June 27, 2019 at 12:59:25 PM UTC+5:30, les...@gmail.com wrote: > > Thanks Kasun, > > One thing th

[go-nuts] Looking for mentors for an open-source event

Hi, At my company, we're organizing a 3 months event in which employees are invited to give back to open-source projects and technologies we're using in the company, Develer! A kind of 3-months contributor workshop if you like... We have already some experienced go developers and contributors

[go-nuts] go vet should warn about a potential non-nil interface with nil value

This happened to me more than once, and not only with errors. For a function that is declared to return an interface, if you return a nil-pointer with a type other than that interface, the returned interface is not nil. Here's an example: https://play.golang.org/p/dpd76zyN9Fv I think go vet sho

[go-nuts] A proof-of-concept implementation of my generics proposal for Go

Hey everybody! A few weeks ago, I posted about my proposal for generics in Go 2. You can find it here. Today, I finished a proof-of-concept implementation. It was a lot of fun and I learned a lot about the internals of Go. The

Re: [go-nuts] go vet should warn about a potential non-nil interface with nil value

It's been discussed a bunch of times - the main argument against remains that "nil" is not a special value and can be a perfectly reasonable implementation of an interface. For example, `sort.StringSlice(nil)` is a perfectly fine implementation of `sort.Interface` (the same, of course, for any othe

Re: [go-nuts] go vet should warn about a potential non-nil interface with nil value

On Thu, Jun 27, 2019 at 8:51 AM Axel Wagner wrote: > > It's been discussed a bunch of times - the main argument against remains that > "nil" is not a special value and can be a perfectly reasonable implementation > of an interface. For example, `sort.StringSlice(nil)` is a perfectly fine > impl

Re: [go-nuts] go vet should warn about a potential non-nil interface with nil value

Can you post some working code to the playground? ISTM that the code you shown wouldn't compile (X has both a Next field and a Next method). Also, the receiver is called X, but you return an *Item. That's not totally hypothetical as a follow-up, because in general, linked lists are an example of wh

Re: [go-nuts] go vet should warn about a potential non-nil interface with nil value

On Thu, Jun 27, 2019 at 10:06 AM Axel Wagner wrote: > > Can you post some working code to the playground? ISTM that the code you > shown wouldn't compile (X has both a Next field and a Next method). Also, the > receiver is called X, but you return an *Item. That's not totally > hypothetical as

Re: [go-nuts] A proof-of-concept implementation of my generics proposal for Go

Syntactically this looks very good. I have read your gist but I'd like to see this as a proposal in the Go issue tracker. Ian On Thu, 27 Jun 2019, at 3:29 PM, Michal Strba wrote: > Hey everybody! > > A few weeks ago, I posted about my proposal for generics in Go 2. You can > find it here. >

Re: [go-nuts] How to build gollvm on arm platform

Hello, For cmake I'd recommend looking at the https://cmake.org/ documentation -- that should give you an overview. We're using cmake with Gollvm since it's the system used by LLVM. If you aren't familiar with building and testing LLVM, that's a good place to start reading, since gollvm is intend

[go-nuts] How to create custom diameter application with go

Hi all, I cannot see diameter messages of my custom diameter application (Application-ID 16777255, code: 8388620) in Wireshark after modifying the go-diameter example server and client codes. Can you explain why am not seeing my custom application AVPs in Wireshark? What I did was to write a

[go-nuts] Diameter application messages not being sent

Hi all, Am trying to implement a diameter application (Application-ID 16777255) using go-diameter package. >From what I have read, to be able to exchange message between diameter peers, these basic steps are required 1. the transport connection (TCP/SCTP) need to be established. 2. CER/CEA mes

Re: [go-nuts] go vet should warn about a potential non-nil interface with nil value

I don't quite understand the logic you are proposing - but my point still stands: I believe you should first try and implement it as a separate tool. There is no real downside to that approach; it's just as useful as its own tool. And with a working implementation, we can concretely check its false

Re: [go-nuts] go vet should warn about a potential non-nil interface with nil value

On Thu, Jun 27, 2019 at 12:10 PM Axel Wagner wrote: > > I don't quite understand the logic you are proposing - but my point still > stands: I believe you should first try and implement it as a separate tool. > There is no real downside to that approach; it's just as useful as its own > tool. An

[go-nuts] A counter proposal to the try proposal - catch

I really don't like the try proposal , because I think it hurts readabiity of the code. But I think the fix is not too hard, so I made a counter proposal, catch: https://github.com/golang/go/issues/32811 Catch works just like try, except it has to be

[go-nuts] Go Blog: Next steps toward Go 2

For those of you who are not actively following the Go Blog , yesterday we have posted a new entry on proposals we are considering for Go 1.14: https://blog.golang.org/go2-next-steps - gri -- You received this message because you are subscribed to the Google Groups "g

Re: [go-nuts] Re: godoc memory leak

wrt tracing out leaks, pprof is insanely powerful and relatively easy to add in. -- 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...@googlegro

[go-nuts] Re: A proof-of-concept implementation of my generics proposal for Go

I really, really like this. I liked the original proposal, but using the "type" keyword seems very natural. And I like the 80/20 constraints thing with eq/ord/num. Good work -- I hope this gets turned into an official proposal and debated. -Ben On Thursday, June 27, 2019 at 10:29:03 AM UTC-4,

[go-nuts] How to compose complex types

If you're curious like me then checkout https://koohinoorgo.blogspot.com/2019/06/compose-complex-types.html -- 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 gola

Re: [go-nuts] Re: A proof-of-concept implementation of my generics proposal for Go

I also like this proposal, and have a related proposal with a somewhat different syntax that is even simpler and is essentially identical to existing Go code, just with “Generic Native Types” (GNT). Here’s a couple of side-by-side comparisons: /// // Min Michal’s: func Min(x,

[go-nuts] I uploaded "Go Installation" videos, English one and Japanese one on youtube.

English one: https://youtu.be/eJU67MZKm0k Japanese one: Japanese ons has more detail. https://youtu.be/jdUJLojDiKw -- 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

[go-nuts] Maven Golang plugin 2.3.2 is released

Maven Golang plugin 2.3.2 is released in maven central. Mainly it is a maintenance release and default GoSDK is updated to 1.12.6. As improvement - its multi-module archetype is updated to support code sharing through maven repository. So if you need some

Re: [go-nuts] How to build gollvm on arm platform

Hi Than, Thanks for your guide, this certainly helps. I don't have any specific questions at the moment. Thanks again. -- 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 em