Re: [go-nuts] [generics] combining different instances of the same generic type

The conversation has drifted a little from generics, I've replied inline below: On Wed, 2 Dec 2020 at 20:56, roger peppe wrote: > On Wed, 2 Dec 2020 at 09:15, roger peppe wrote: > >> Also your delayed blocks don't wait for the preceding set of futures to >>> be exhausted before proceeding, I th

Re: [go-nuts] Can we "go get" unreleased standard library packages?

$ git checkout master in source tree provide me `io/fs` On Thu, Dec 3, 2020 at 3:10 AM 'Axel Wagner' via golang-nuts < golang-nuts@googlegroups.com> wrote: > No, that's not really possible. The stdlib is packaged with the Go > compiler and is very interdependent. > It also wouldn't help you a l

Re: [go-nuts] Can we "go get" unreleased standard library packages?

Ah, that's a great point. Thanks for taking the time to explain it! I'll wait for the beta then – thanks! On Thursday, December 3, 2020 at 1:10:51 AM UTC+1 axel.wa...@googlemail.com wrote: > No, that's not really possible. The stdlib is packaged with the Go > compiler and is very interdependen

Re: [go-nuts] Can we "go get" unreleased standard library packages?

No, that's not really possible. The stdlib is packaged with the Go compiler and is very interdependent. It also wouldn't help you a lot, because in go1.15, the `io/fs` package has no implementation yet. For example, (*os.File).Stat does not return the correct type, compare https://tip.golang.org/pk

[go-nuts] Can we "go get" unreleased standard library packages?

Hey there, I'd like to try the io/fs package on Go 1.15. Is there an easy way to do this? I tried without much expectation: go get -u github.com/golang/go/src/io/fs But was greeted with this error: go: found github.com/golang/go/src/io/fs in github.com/golang/go/src v0.0.0-20201202201757-2d02

[go-nuts] Re: [error handling] RFC 'else'

see also https://github.com/golang/go/issues/41908 https://github.com/golang/go/issues/37243 https://github.com/gooid/gonotes/blob/master/inline_style_error_handle.md On Wednesday, December 2, 2020 at 8:57:13 PM UTC+1 Oliver Smith wrote: > Do I understand correctly that "last return value is err

[go-nuts] [error handling] RFC 'else'

Do I understand correctly that "last return value is error" is purely convention and there is no formal error handling in current go? My instinct is to leverage the 'else' keyword along with the notion of a "stock error whose return list's last element is type error with value != nil. func n

[go-nuts] is "foo.com" a valid module path/name?

Can't seem to find any info on the topic so asking here. Is it expected for "import foo.com" to be valid for modules? Or are modules required to not be the root url? -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group

[go-nuts] Announcing Fibratus - a modern tool for the Windows kernel exploration and tracing

Hi fellow Gophers I'm thrilled to announce Fibratus - a modern tool for the Windows kernel tracing and observability built in Go. *Fibratus* is the fruit of a lot of development and research during the past two years. To discover more about Fibratus,

Re: [go-nuts] [generics] combining different instances of the same generic type

On Wed, 2 Dec 2020 at 09:15, roger peppe wrote: > Also your delayed blocks don't wait for the preceding set of futures to be >> exhausted before proceeding, I think they're all triggered once the initial >> set is completed > > > Each delayed block is triggered when its associated delay has elaps

Re: [go-nuts] [generics] combining different instances of the same generic type

> > Also your delayed blocks don't wait for the preceding set of futures to be > exhausted before proceeding, I think they're all triggered once the initial > set is completed Each delayed block is triggered when its associated delay has elapsed. Once the initial set is completed, it returns imme

Re: [go-nuts] History & origins of the Go memory model

Thanks for this bit of history, Ian! I’ve been studying the memory model in grad school for a few years now and I think it’s well written. I was curious about how it came to be. I think the “completes” also mater for buffered channels, for example: https://github.com/golang/go/issues/37355