* Debarshi Ray via devel:

> This tendency of Go modules (used as dependencies) to keep updating the
> required Go version has started to bother me in recent times.  It
> doesn't look like the Go toolchain strictly enforces the version,
> because I remember trying to build with an older version and
> succeeding, or maybe I am misremembering?

With our without an Internet connection?

| For example, when using the go command bundled with Go 1.21.3 in a
| main module that says go 1.21.9, the go command finds and runs Go
| 1.21.9 instead. It first looks in the PATH for a program named
| go1.21.9 and otherwise downloads and caches a copy of the Go 1.21.9
| toolchain.

<https://go.dev/doc/toolchain>

Automatic downloading of newer toolchain can paper over lots of
compatibility issues.

Thanks,
Florian

-- 
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to