On Wed, 2022-08-10 at 11:17 -0700, Mike Schinkel wrote: > In my experience having control over the implementation is not a > black-and-white thing, unless you are the sole developer on a > project.
This also brings in the consideration of that if you have complete control over the implementation, why do you need to enforce this kind of encapsulation so strictly? The other question is why does that encapsulation need to happen at the boundary of the producer of the data rather than at the boundary of the consumer of the data? In my experience, functions that return interfaces egregiously (they are doing it for this kind of encapsulation) generally make my work harder when I am debugging, and make code comprehension significantly harder. Dan -- 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/7649a414b3dc3f7ac3f7252b03ec9f92d8e5aaac.camel%40kortschak.io.
