Justin Isreael said "Changes to ProjectB should be immediately available when compiling ProjectA."
which is not true when you simply insert a replace in your go.mod file. My current problem is that I have a main module that uses a library module. I want to debug an issue so I insert a print statement in my main module. That works. But now I want to insert a print statement in the library. How do I do that? 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? -- 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/421ae2eb-fd97-46b4-ab83-979c5e63cf88n%40googlegroups.com.
