Inline cost is part of how Go decides what funcs to inline. There are some
interesting patterns (maybe even idioms?) in Go that specifically try to
inline a lot of code to prevent values from escaping to the heap when they
don't have to. Concrete examples from -gcflags='-m -m':
./main.go:7:6: c
See the section wrapped in """ in Jan's reply. Quoted differently:
> A parsing ambiguity arises when a composite literal using the TypeName
form of the LiteralType appears as an operand between the keyword and the
opening brace of the block of an "if", "for", or "switch" statement, and
the comp
Recently I noticed that https://pkg.go.dev takes you to the main/search
page, but https://go.dev/pkg takes you right to https://pkg.go.dev/std. It
seems like some quirk of the go.dev/pkg redirect, but maybe an interesting
shortcut if you like typing in a short URL.
On Monday, February 3, 2025 at
ue, Sep 3, 2024 at 10:59 AM 'Davis Goodin' via golang-nuts
> wrote:
> >
> > I noticed today that taking the Go 1.22.6 source tree and running
> "go1.22.6 mod vendor" and "go1.23.0 mod vendor" give me different results.
> (Vendoring using go1.23
I noticed today that taking the Go 1.22.6 source tree and running "go1.22.6
mod vendor" and "go1.23.0 mod vendor" give me different results. (Vendoring
using go1.23.0 adds golang.org/x/crypto/sha3.)
I've been working under the assumption that backward compatibility promises
would extend to "go
Yes, these questions are specific to the Microsoft fork of Go (and to
varying degrees, could apply to other FIPS-focused forks of Go). To repeat
from earlier, in case it helps anyone seeing this thread later:
> The GOEXPERIMENT=systemcrypto is a feature of the Microsoft fork of Go,
not official
