# Julep: Taking multiple dispatch,export,import,binary compilation seriously

**URL:** <https://discourse.julialang.org/t/julep-taking-multiple-dispatch-export-import-binary-compilation-seriously/10882>\
**Category:** Internals & Design\
**Tags:** namespaces\
**Created:** [May 14, 2018, 9:58am UTC](https://discourse.julialang.org/t/julep-taking-multiple-dispatch-export-import-binary-compilation-seriously/10882 "2018-05-14T09:58:33Z")\
**Posts on this page:** 1\
**Showing post:** 115

<div class="post-metadata">

**Author:** ![davidanthoff](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/davidanthoff/32/223493_2.png) [@davidanthoff](https://discourse.julialang.org/u/davidanthoff)\
**Post date:** [May 17, 2018, 4:50pm UTC](https://discourse.julialang.org/t/julep-taking-multiple-dispatch-export-import-binary-compilation-seriously/10882/115 "2018-05-17T16:50:10Z")

</div>

I didn’t follow all of this thread, so apologies if the following is off. But one thing that I often wish we had is a syntax that allows me to import a package and assign a different local name to it in one go. So essentially a shortcut for `import Foo; const bar = Foo`.

Typescript has something similar (`import * as bar from "Foo"`) and Python of course has the alias syntax (`import Foo as bar`). I find both of these extremely useful.

I think it would allow us to a) keep the long and descriptive package names we seem to tend towards (I like that!) and b) generally use `using` less, but still have relatively concise code.

And yes, obviously one can use the syntax I showed above, but I think it would be nice if there was official syntax for this.

---

_[View the full topic](https://discourse.julialang.org/t/julep-taking-multiple-dispatch-export-import-binary-compilation-seriously/10882)._