On Mon, Jul 4, 2016 at 8:11 AM, Jon Bodner <j...@bodnerfamily.com> wrote: > > The issue you pointed at is exactly what I'd like to see. > > In my case, I'm providing an interface that matches what's in database/sql > without creating an explicit dependency on database/sql (for cases when > non-sql databases, or non-databases are used for data storage). I think this > is a pretty common pattern in Go, writing code that consumes interfaces > defined within the same project, even if the methods are identical to those > on an interface in a third-party package. > > What would I need to do to get more consideration for including #16209 in Go > 1.8?
It's a language change, and any change must be considered very carefully. It must also, of course, be completely backward compatible. It would help to understand real use cases. It would also help to understand the drawbacks of the proposal. 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.
