title: Two Modules, both exporting the same name
body: <p>There are two packages I want to use: <a href="https://github.com/oxinabox/CorpusLoaders.jl/" rel="nofollow">CorpusLoaders.jl</a>, and <a href="https://github.com/jbn/WordNet.jl" rel="nofollow">WordNet.jl</a></p>
  
  <ul>
  <li>CorpusLoaders.SemCor exports <code>sensekey(::SenseTaggedWord)</code></li>
  <li>WordNet exports <code>sensekey(::DB, ::Synset, ::Lemma)</code></li>
  </ul>
  
  <p>I want to use both <code>sensekey</code> methods.</p>
  
  <p>Eg</p>
  
  <p>for some mixed list of items: <code>mixedlist::Vector{Union{Tuple{SenseTaggedWord},Tuple{DB, Synset,Lemma}}</code>.
  Ie the items in the list are a mixture of 1-tuples of <code>SenseTaggedWord</code>, and3 tuples of <code>DB</code>, <code>Synset</code>, and <code>Lemma</code>.</p>
  
  <pre><code>for item in mixedlist
      println(sensekey(item...)
  end
  </code></pre>
  
  <p>should work.
  This example is a little facetious, since why would I be mixing them like this.
  But, hopefully it serves for illustrating the problem in the general case.</p>
  
  <p>Trying to <code>using CorpusLoaders.SemCor, WordNet</code> to bring in both results in <code>WARNING: both WordNet and Semcor export "sensekey"; uses of it in module Main must be qualified.</code></p>
  
  <p>Manually importing both: <code>import CorpusLoaders.SemCor.sensekey; import WordNet.sensekey</code>  results in <code>WARNING: ignoring conflicting import of Semcor.sensekey into Main</code></p>
  
  <p><strong>What can be done? I want them both, and they don't really conflict, due to multiple-dispatch.</strong></p>
  
  <hr>
  
  <p>Given that CorpusLoaders.jl is a package I am writing I do have a few more options, since I could make my CorpusLoaders.jl depend on WordNet.jl.
  If I did do than then I could say in CorpusLoaders.jl </p>
  
  <pre><code> import WordNet
   function WordNet.sensekey(s::SenseTaggedWord)...
  </code></pre>
  
  <p>and that would make them both work.
  But it would mean requiring WordNet as a dependency of CorpusLoaders.</p>
  
  <p>And I want to know how to solve the problem for a consumer of the packages -- not as the creator of the packages.</p>
  
  <p></p>