On Tue, Feb 23, 2021 at 5:03 PM 'simon place' via golang-nuts < golang-nuts@googlegroups.com> wrote:
> nothing compiles any more! > > i seem to be being forced to add, to some projects 9 years old > (unnecessary) module support, or, add notes to all their docs that they > need to be compiled in versions older than 1.16, or have to have an obscure > parameter set. > > there really wasn't a non-breaking way to do this? > > seems to me this has effectively become part of the language and should be > implemented in accordance with the go1 backward compat. guarantee. what > difference does it make to a user when things stop compiling like this. > On Tuesday, 16 February 2021 at 19:56:37 UTC Alex Rakoczy wrote: > Insufficient information. What command did you run? What was the output? Note that module mode is now the default with Go 1.16. You can get the Go 1.15 behavior by exporting GO111MODULE=auto. However, that will just punt the problem down the road. At some point in the future GOPATH mode will no longer be supported. You're probably better off biting the bullet now and switching to Go modules. P.S., Note that I deliberately changed the subject line to start a new thread. -- Kurtis Rader Caretaker of the exceptional canines Junior and Hank -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CABx2%3DD-SN5zmTGtsNJDYsCq-hor6nYUu24QxN5sRUwjiyZLOBQ%40mail.gmail.com.
