On Thu, Nov 24, 2016 at 6:01 AM, T L <tapir....@gmail.com> wrote: > > On Thursday, November 24, 2016 at 8:16:49 AM UTC+8, Ian Lance Taylor wrote: >> >> On Wed, Nov 23, 2016 at 3:49 PM, roger peppe <rogp...@gmail.com> wrote: >> > Ian, what you say is true, but is also true of types and other objects >> > too, >> > I think. I found some interesting anomalies playing around with the new >> > plugin package. >> >> We've worked hard to make sure that what I said earlier is not true of >> types, even in the presence of shared libraries. If we've failed, >> please file bugs. Even with plugins it should work correctly. > > > so os.File from a plugin is the same as the os.File in the host program? > how do we know the os package from a plugin is the same package in the host > program?
In a Go program, the path used in the import statement uniquely defines a package. If you write a plugin that breaks that rule, your plugin will not work correctly. 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.
