3 ms·

Note the word “programs”, not “files”. If your program doesn’t declare go 1.22 in its go.mod, it will continue to work (or not work!), unchanged.

• robertlagrant 3y ago
  Isn't that "working with future point releases", though? If I don't declare 1.22, am I not excluded from that point release?
  • ben0x539 3y ago
    I assume that if compiling with 1.22 or later, you still get all the benefits from that version like other new features, bug fixes or perf improvements, just not this particular change.
  • mrkstu 3y ago
    No, the compiler will revert to the original behavior, it only adopts the new behavior with the declaration.
  • skywhopper 3y ago
    This has all been addressed in the proposal. The research was done and this change will impact so few projects that it’s worth making a technical exception to the compatibility promise to fix a real design flaw.