Harmen once said:
> It all works fine, just wondering if there's a nicer way to get all
> "compilable" packages stored in /vendor.
go list ./vendor/...
Cheers,
Anthony
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this
Robert Engels once said:
> I think you’ll find the article interesting. It is certainly written
> by a CS “god” that knows what he’s talking about.
This is the same "god" that said:
"Everyone thinks that the concurrency model is Go’s secret
weapon, but I think their concurrency
Rory Campbell-Lange once said:
> interface conversion: *zip.checksumReader is not io.ReadSeeker:
> missing method Seek
>
> Advice on how to rectify this would be gratefully received.
Read the entire zip.File into memory with io.ReadAll and create
a bytes.Reader with the resulting byte slice.
Yes, let's support everyone!
If any gopher from the DNR or LNR is tired of their plight
being ignored and wants to chat with a friendly US citizen
from California, feel free to email me.
Anthony
--
You received this message because you are subscribed to the Google Groups
"golang-nuts"
Jesper Louis Andersen once said:
> On Fri, Apr 9, 2021 at 5:37 PM 'Petite Abeille' via golang-nuts <
> golang-nuts@googlegroups.com> wrote:
> >
> > Would you know of any go text://protocol clients? Or servers?
> >
> >
> No, but it would be a fairly good beginner project[0]
>
> [0] Readers of the
can...@google.com once said:
> After review, permanent bans were given to multiple individuals, with no
> possibility for appeal. Further corrective actions like temporary bans and
> final warnings are being deliberated, pending further investigation.
Where is the moderation log?
Anthony
--
Katie Hockman once said:
> The Reader.Open API, new in Go 1.16, will panic when used on a ZIP archive
> containing files that start with “../”.
>
> This issue is CVE-2021-27919 and Go issue golang.org/issue/44916.
Should I submit a CVE request for the power switch on my
server? Prodding it with
https://www.bell-labs.com/usr/dmr/www/labscam.html
Cheers,
Anthony
--
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...@googlegroups.com.
> Tasteless attempt at humour.
Our collective taste is ruined by the
anosmia of a contemporary disease.
Anthony
--
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
'Axel Wagner' via golang-nuts once said:
> What isn't welcome is your attempt of alienating people with a different
> viewpoint from yours and make them feel unwelcome. And if you continue to
> insist on doing that, the community *will* ask you to leave.
Please don't minimize or silence the
saurav deshpande once said:
> How to implement macro in plan9 assembly? I read the documentation of
> plan9 assembly but could not find it. Is there any alternative for
> macro in plan9?
Assembly language source files are preprocessed just like C source.
The familiar #define and #include
Matthew Zimmerman once said:
> I've also thought about authenticating on a different domain name
> auth.service then redirecting to data.service or something like that where
> the cookie would be issued to the *.service domain, however that's still
> one tls.Config and using SNI with
Katie Hockman once said:
> The Go 1.13.2 release also includes a fix to the compiler that prevents
> improper access to negative slice indexes in rare cases. Affected code, in
> which the compiler can prove that the index is zero or negative, would have
> resulted in a panic in Go 1.12.11, but
Prabhash Rathore once said:
> Looking at comment, it seems Golang does not support SSLv2 and SSLV3.
The crypto/tls package can support SSLv3 if you set tls.Config.MinVersion
to tls.VersionSSL30, but only as a server.
> I am reaching out to see if there is anyway possible to add support for
>
Sam Whited once said:
> This is especially a problem when these proposals further tie Go to
> Google web services run by the Go team (though I'm veering off into a
> separate problem here). To me this feels like it's almost a type of
> vertical integration and it's an absolutely disgusting thing
Ian Lance Taylor once said:
> I don't *think* the format string is changing. I think the 0 is from
> the string being printed, not the format string. They both happen to
> be length 5.
Misled by the pair of fives. Mea culpa.
Anthony
--
You received this message because you are subscribed
What version of Go are you using?
XXX ZZZ once said:
> fmt.(*pp).fmtString(0xc023c17740, 0x0, 0x5, 0xc00076)
> /usr/local/go/src/fmt/print.go:448 +0x132
> fmt.(*pp).printArg(0xc023c17740, 0x9978e0, 0xc016a68a30, 0x76)
> /usr/local/go/src/fmt/print.go:684 +0x880
>
A hash function is a mathematical construction.
A raster image is a type of graphical representation.
A time instant is a single point in a duration.
All of these are clear as can be.
I'll give you "context frame". It is a bit wonky.
A better phrase is out there somewhere. Scope,
environment,
Mark Volkmann once said:
> Suppose myPtr is a pointer and I write code like this:
>
> for _, v := range values {
> fmt.Printf("%v %v\n", *myPtr, v)
> }
>
> Will the Go compiler optimize the pointer dereference so it doesn't happen
> in every loop iteration? If not, is it common practice to do
Nigel Tao once said:
> Well, there's already context.Context, hash.Hash, image.Image and
> time.Time in the standard library.
All of which are not great. Better names are context.Frame,
hash.Function, raster.Image, and time.Instant.
Anthony
--
You received this message because you are
20 matches
Mail list logo
