# Should modules no longer use \_\_precompile\_\_()?

**URL:** <https://discourse.julialang.org/t/should-modules-no-longer-use-precompile/13660>\
**Category:** Internals & Design\
**Created:** [August 18, 2018, 12:08pm UTC](https://discourse.julialang.org/t/should-modules-no-longer-use-precompile/13660 "2018-08-18T12:08:14Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![galenlynch](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/galenlynch/32/17947_2.png) [@galenlynch](https://discourse.julialang.org/u/galenlynch)\
**Post date:** [August 18, 2018, 12:08pm UTC](https://discourse.julialang.org/t/should-modules-no-longer-use-precompile/13660/1 "2018-08-18T12:08:14Z")

</div>

Reading the docs for 0.7, only ` __precompile__ (false)` is mentioned. It seems like modules are now precompiled be default, so is putting a ` __precompile__ ()` statement at the top of a module still recommended?

---

<div class="post-metadata">

**Author:** ![favba](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/favba/32/2735_2.png) [@favba](https://discourse.julialang.org/u/favba)\
**Post date:** [August 18, 2018, 12:13pm UTC](https://discourse.julialang.org/t/should-modules-no-longer-use-precompile/13660/2 "2018-08-18T12:13:39Z")

</div>

I think you still need that if you want your module to work the same way both with v0.6 and \>v0.7.

---

<div class="post-metadata">

**Author:** ![galenlynch](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/galenlynch/32/17947_2.png) [@galenlynch](https://discourse.julialang.org/u/galenlynch)\
**Post date:** [August 18, 2018, 2:17pm UTC](https://discourse.julialang.org/t/should-modules-no-longer-use-precompile/13660/3 "2018-08-18T14:17:45Z")

</div>

Thanks!