`using` a package that uses `OrderedCollections` can silently add function methods?

[rdeits]

@tomohiro_soejima

I initially thought modules that are called inside a package wouldn’t be an issue because it’s separated by two using s (I call Revise which calls OrderedCollections ), but I suppose that is not the case?

No, that has no effect. There is only ever one instance of a given module, so the OrderedCollections inside Revise is the same one you get everywhere else (it is possible to have two unrelated modules with the same name, but that’s unrelated to what’s going on here).

@tomohiro_soejima

As a follow-up question, does this mean there is nothing users can do to protect ourselves from type piracy, other than to hope they don’t exist?

You might try Pirate Hunter (I haven’t used it myself)

@tomohiro_soejima

In other words, not only do I need to hope a package I load is not committing type piracy, but I also need to hope all dependencies of the package did not commit type piracy?

Basically yes. In my experience, this is rarely a problem, but it is something to be aware of.