[go-nuts] Re: Delve v1.24.2 release!

Absolute life saver! Thanks to all who contributed to fixing the Sequoia issue! On Friday, 11 April 2025 at 04:24:07 UTC+12 Derek Parker wrote: > Hello Gophers, > > Just wanted to announce that Delve v1.24.2 > > has

Re: [go-nuts] Re: How to know if interface{} data is nil w/o reflecting?

I don't believe this is contradictory. TL;DR: `error` is a (very) special case, part of the language specification itself. Long-form (my take): The guidance in CodeReviewComments relate to interface types and any implementation defined by a project. The guidance in faq#nil_error relates to c

Re: [go-nuts] Imitating tuple in golang

My $0.02 on this First, to address the use cases in your question, Golang does not have custom operators so the value of tuples in assisting with their implementation is moot. (and, IMHO, should resist incorporating them; someone should not have to consult the source for a type to understand w

Re: [go-nuts] Re: go mod conflict whith v2 pre-release

p, I hadn't noticed the significance of >> the tag. :-) >> >> Your reply introduced a new aspect: how does the go-get mechanism handle >> packages that are not tracked in the master branch of the version control >> system? >> >> >> >&g

Re: [go-nuts] Re: go mod conflict whith v2 pre-release

Is this the correct approach to major-v-bumping a module? I had understood the "vN" slug in the module to be a "virtual" element, signalling the deliberate introduction of an upgrade to a new major version of a dependency. i.e. it avoids (or at least makes less likely) the chance of inadverte