# Query compiler's effect modeling

**URL:** <https://discourse.julialang.org/t/query-compilers-effect-modeling/134079>\
**Category:** Performance\
**Tags:** question, compilation\
**Created:** [November 24, 2025, 1:50pm UTC](https://discourse.julialang.org/t/query-compilers-effect-modeling/134079 "2025-11-24T13:50:43Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tamas\_Papp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tamas_papp/32/25949_2.png) [@Tamas\_Papp](https://discourse.julialang.org/u/Tamas_Papp)\
**Post date:** [November 24, 2025, 1:50pm UTC](https://discourse.julialang.org/t/query-compilers-effect-modeling/134079/1 "2025-11-24T13:50:43Z")

</div>

Before using `@assume_effects`, is it possible to check what the compiler already figured out about a function?

I can of course do it very indirectly (call the function and see what’s eliminated), but it would be great to do it directly, using a call signature.

---

<div class="post-metadata">

**Author:** ![Oscar\_Smith](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/oscar_smith/32/25343_2.png) [@Oscar\_Smith](https://discourse.julialang.org/u/Oscar_Smith)\
**Post date:** [November 24, 2025, 1:54pm UTC](https://discourse.julialang.org/t/query-compilers-effect-modeling/134079/2 "2025-11-24T13:54:03Z")

</div>

`Base.infer_effects`.

---

<div class="post-metadata">

**Author:** ![Sukera](https://avatars.discourse-cdn.com/v4/letter/s/ce7236/32.png) [@Sukera](https://discourse.julialang.org/u/Sukera)\
**Post date:** [November 24, 2025, 2:15pm UTC](https://discourse.julialang.org/t/query-compilers-effect-modeling/134079/3 "2025-11-24T14:15:46Z")

</div>

Be careful with using this in CI though, as code coverage has an influence on the inferred effects. See also [Effects on master are influenced by generation of coverage data · Issue #49978 · JuliaLang/julia · GitHub](https://github.com/JuliaLang/julia/issues/49978)