On Friday, 9 April 2021 at 17:38:12 UTC+2 gonutz wrote: > A replace in the go.mod file is of no help here because I still have to > specify a require with a concrete version or commit hash for the library. > This means I cannot just change the code in the library module, I also have > to create a commit and check it in, then go back to my main module and > udpate not only the replace but also the require in go.mod, every time I > want to simply place a simple, temporary print statement for debugging > purposes into the library. > > Does anybody have an easy workflow for the common use case? >
https://golang.org/doc/modules/managing-dependencies#local_directory -- 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/7eb50cc0-9244-4169-80db-3d03fd2e017fn%40googlegroups.com.