# Fine grained control of \_\_precompile\_\_(false)?

**URL:** <https://discourse.julialang.org/t/fine-grained-control-of-precompile-false/124811>\
**Category:** General Usage\
**Tags:** package, packages, precompilation, precompile\
**Created:** [January 15, 2025, 9:26pm UTC](https://discourse.julialang.org/t/fine-grained-control-of-precompile-false/124811 "2025-01-15T21:26:39Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Benny](https://avatars.discourse-cdn.com/v4/letter/b/49beb7/32.png) [@Benny](https://discourse.julialang.org/u/Benny)\
**Post date:** [January 17, 2025, 1:29am UTC](https://discourse.julialang.org/t/fine-grained-control-of-precompile-false/124811/3 "2025-01-17T01:29:52Z")

</div>

Looking at that linked comment, you’re overwriting a `LibPQ` method from your package. Besides dynamic method overwriting being impossible to implement well among precompiled packages, this is a subset of type piracy that risks broken behavior among and within modules, precompiled or not. It might be worth making a separate thread for advice on refactoring.

---

_[View the full topic](https://discourse.julialang.org/t/fine-grained-control-of-precompile-false/124811)._
