[go-nuts] Go Boring release schedule

Hey there, Go 1.17 was released last week (Aug 16th), but it appears the corresponding build of Go + Boring Crypto is not available yet (checking the Google Cloud Storage bucket as well as Docker Hub). Does anyone know if these releases typically track the main upstream Go closely, or if releases

Re: [go-nuts] Using a local copy of an external package?

Oops, I see another reply to this thread linked to a document that has a better description of what I stumbled through. :-) Connor -- 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

Re: [go-nuts] Using a local copy of an external package?

> On Aug 26, 2021, at 5:21 PM, Paul S. R. Chisholm > wrote: > > Hypothetical example: Say I'm writing an application that uses "rsc.io/quote" > and I discover a bug in that package that breaks my software. I would of > course clone the quote repository, add a test that demonstrates the

Re: [go-nuts] write func with optional bool return value

Ok, thank you for the clarification пт, 27 авг. 2021 г. в 18:18, Axel Wagner : > > No, it is not possible. The *only* functions that can return either one or > two returns are builtins. > That's because the number of returns is part of the type of a function, so it > is constant for every

Re: [go-nuts] write func with optional bool return value

No, it is not possible. The *only* functions that can return either one or two returns are builtins. That's because the number of returns is part of the type of a function, so it is constant for every function. Builtin "functions", OTOH, are not really functions, in terms of the language. They are

Re: [go-nuts] write func with optional bool return value

I know, so my question is - does it possible to write such functions like builtin? For example I can create func via reflect пт, 27 авг. 2021 г. в 18:03, Levieux Michel : > > Hi, > > Optional returns and parameters don't exist in go, what you are referring to > is built-in behavior specific

Re: [go-nuts] write func with optional bool return value

Hi, Optional returns and parameters don't exist in go, what you are referring to is built-in behavior specific to some features. A good way to approach what you want is by assigning it to the anonymous '_' var when you don't want the returned bool. Hope this helps Le ven. 27 août 2021 à 16:58,

[go-nuts] write func with optional bool return value

Does it possible to have own func that have string, bool return value, but bool value optional? Like receiving from channel or get element from map, or like when casting to some type interface? -- Vasiliy Tolstov, e-mail: v.tols...@selfip.ru -- You received this message because you are

[go-nuts] fonts, bitmap and the (old TeX) PK file format

hi there, I am working on providing a pure-Go TeX engine. to achieve such a thing, I'd need to be able to decode and use the so-called "PacKed font file" format (PK fonts). (I know it's a very old & deprecated file format, but I figured it would be easier on me to start "old tech" first) I think

[go-nuts] Re: 'go vet' not finding methods exported in _test.go files?

I can't reproduce the error you're seeing either in 1.15 or in later versions with the code you provided On Friday, August 27, 2021 at 10:11:07 AM UTC+2 wji...@gmail.com wrote: > Hi, > > We've recently moved from using 'go tool vet' to 'go vet' (we need to > stick to the Go versions shipped

[go-nuts] 'go vet' not finding methods exported in _test.go files?

Hi, We've recently moved from using 'go tool vet' to 'go vet' (we need to stick to the Go versions shipped with Debian) and have found that it is not finding public methods that we export for test only by putting them in _test.go files (error is 'undeclared name'). Disable go vet, and you can