On Sat, Aug 25, 2018 at 7:58 AM, Peter Kleiweg <pklei...@xs4all.nl> wrote: > Op zaterdag 25 augustus 2018 16:40:55 UTC+2 schreef Jakob Borg: >> >> On 25 Aug 2018, at 15:21, Peter Kleiweg <pkle...@xs4all.nl> wrote: >> >> >> disabling the cache won't be an option in Go 1.12. What to do then? >> >> >> You don’t say what your issues with the build cache are. If you did, you >> might get suggestions. > > > Actually, setting GOCACHE=off doesn't solve all problems. So I am now back > to Go version 1.9.7 > > Some problems: > > - You can't use packages that require local adjustments to the environment > to install.
Can you expand on this. I'm not sure what you mean. > - Code completion in Emacs doesn't work (using gocode) That sounds like a bug to be fixed. The golang.org/x/go/packages package is intended to use the build cache for input where appropriate. The likely path forward will be to make gocode use go/packages. > - Running Go in a Jupyter Notebook (using lgo) is slow with Go version 1.10 > and higher. I don't know what lgo is. In general the cache does not slow down the build. Quite the opposite: in my experience, it speeds it up. If you see cases where the cache makes things slower, please report them so that they can be fixed. Ian -- 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. For more options, visit https://groups.google.com/d/optout.
