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

As a matter of fact, I gained a somewhat complete understanding of the whole concept of Go modules and the go-get facade mechanism through writing a simple pkgsvr (https://xrfang.coding.net/public/go/pkgsvr/git/files). However, before this issue came up, I hadn't noticed the significance of the ta

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

Re: [go-nuts] Is it possible to "extract" the generic [T] from a reflected type ?

If I understand correctly, the restriction is that the compiler has to know all possible instantiations of a generic func/type/etc at compile time. So listing out each specific Hello instantiation is the workaround, which allows you to approximate this if you have a closed set of types you want

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

Yeah. After clean modcache. Thanks! Jason Phillips 于2024年4月17日周三 22:41写道： > It works for me, now. > > > go get go.xrfang.cn/hap/v2@v2.0.0-alpha.2 > go: downloading go.xrfang.cn/hap/v2 v2.0.0-alpha.2 > go: go.xrfang.cn/hap/v2@v2.0.0-alpha.2 requires go >= 1.22.1; > switching to go1

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

It works for me, now. > go get go.xrfang.cn/hap/v2@v2.0.0-alpha.2 go: downloading go.xrfang.cn/hap/v2 v2.0.0-alpha.2 go: go.xrfang.cn/hap/v2@v2.0.0-alpha.2 requires go >= 1.22.1; switching to go1.22.2 go: upgraded go 1.22.0 => 1.22.1 go: added toolchain go1.22.2 go: added g

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

Hi Jason, Acutally I wrote the go hosting service myself. According to your comments, I modified the output now it is: $ curl https://go.xrfang.cn/hap/v2?go-get=1 https://e.coding.net/xrfang/go/hap.git";> But it still not working: $ GOPROXY=direct go get -v -x -u go.xrfang.cn/hap/v2@v2.0.0-alph

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

I believe the hosting provider is returning a meta tag for "go.xrfang.cn/hap/v2" when it shouldn't? > curl https://go.xrfang.cn/hap/v2?go-get=1 https://e.coding.net/xrfang/go/hap.git";> The above meta tag says that the "go.xrfang.cn/hap/v2" module is at the root of the repository, but it'

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

Hello, I am developing version 2 of my hap package, which is a HTTP API framework. Version 2 is not ready yet, and the latest release ls v2.0.0-alpha.2, like so: * 9319436 - bug fix, refined action error output (H