If you mean forking their dependencies and rewiring their import paths, that is a possibility. But it leaves consumers of those packages in the same position as the thread the OP referenced because the same code is now known by two distinct import paths breaking type equality.
-- 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.
