# In a set of related packages, where is pre-compilation best done?

**URL:** <https://discourse.julialang.org/t/in-a-set-of-related-packages-where-is-pre-compilation-best-done/85375>\
**Category:** General Usage\
**Tags:** question, package, precompilation\
**Created:** [August 6, 2022, 1:49am UTC](https://discourse.julialang.org/t/in-a-set-of-related-packages-where-is-pre-compilation-best-done/85375 "2022-08-06T01:49:02Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Alec\_Loudenback](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/alec_loudenback/32/278_2.png) [@Alec\_Loudenback](https://discourse.julialang.org/u/Alec_Loudenback)\
**Post date:** [August 6, 2022, 1:49am UTC](https://discourse.julialang.org/t/in-a-set-of-related-packages-where-is-pre-compilation-best-done/85375/1 "2022-08-06T01:49:02Z")

</div>

I am in the process of abstracting out some core functionality and methods from packages in the [JuliaActuary](https://juliaactuary.org/) ecosystem into a “Core” package.

Is it always good to precompile code where it’s defined? E.g. in the “Core” package? Or does it depend on factors like:

1. If child packages extend types/methods from “Core”.
2. The user-facing child package `@reexport`s types/functions from “Core”

Thanks in advance for advising on best practices.