<p>What are people's thoughts on abusing type aliases to shorten imported types?</p>
<p>For example, I am using <code>github.com/gopherjs/jquery</code> in a project. It defines <code>jquery.JQuery</code>. I defined a type alias
<code>
type JQuery = jquery.JQuery
</code>
Granted, <code>jquery.JQuery</code> is not much to type, but one can argue that having the package name clutters up the code.</p>
<p>Comments?</p>
<hr/>**评论：**<br/><br/>Lewisham: <pre><p>Don't do this. You're rubbing against the Go idiom of explicit is better than implicit. You're abstracting your types and then forcing readers to go looking to see what your types are.</p></pre>wiiittttt: <pre><p>If anything, you can just shorten the import name.</p>
<pre><code>import (
jq "ithub.com/gopherjs/jquery"
)
</code></pre>
<p>I don't really think using a type alias makes a lot of sense for this personally.</p></pre>excalib_: <pre><p>Don't abuse</p></pre>
