Thanks! This is a pitfall that doesn't come up often, but would arise when
"polyfilling" later behavior into an earlier version, in conjunction with
version build tags.
It's something I'll need to keep in mind in the future.
-- Kevin
On Saturday, November 4, 2023 at 7:19:29 PM UTC-6 Kurtis
On Sat, Nov 4, 2023 at 5:05 PM 'Kevin Gillette' via golang-nuts <
golang-nuts@googlegroups.com> wrote:
> My unconfirmed, but perhaps mistaken understanding of the `go` directive
> in a go.mod file was that it covered both the language and the stdlib.
>
Yes, you are mistaken :-) See
Hello!
My unconfirmed, but perhaps mistaken understanding of the `go` directive in
a go.mod file was that it covered both the language and the stdlib. Since
the stdlib docs indicate the version a given symbol was introduced, and
since build processes validate that signature breakages do not
