# Is there @code\_warntype output documentation anywhere?

**URL:** https://discourse.julialang.org/t/is-there-code-warntype-output-documentation-anywhere/54506
**Category:** Probabilistic Programming
**Tags:** documentation, code\_warntype
**Created:** [February 3, 2021, 2:14am UTC](https://discourse.julialang.org/t/is-there-code-warntype-output-documentation-anywhere/54506 "2021-02-03T02:14:12Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![ElOceanografo](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/eloceanografo/32/624_2.png) [@ElOceanografo](https://discourse.julialang.org/u/ElOceanografo)
#### Post date: [February 3, 2021, 3:27am UTC](https://discourse.julialang.org/t/is-there-code-warntype-output-documentation-anywhere/54506/3 "2021-02-03T03:27:01Z")

</div>

Welcome @zenkavi! The Turing `@model` macro rewrites your model code (i.e., the tilde `~` statements etc.) into straight Julia code, which requires generating/mangling variable names in the process. Hence, using `@code_warntype` on a Turing model is harder to read than normal, an issue I run into myself pretty frequently. My only useful advice is to read through the output carefully, starting with the block at the top (where all the variables are listed with their original names). Often I can figure out which ones are causing issues from that section, then go back to reread my own code to try and figure out where any type instabilities came from.

If you can supply a [MWE](https://discourse.julialang.org/t/psa-make-it-easier-to-help-you/14757) of your model, we may be able to help debug it…

---

_[View the full topic](https://discourse.julialang.org/t/is-there-code-warntype-output-documentation-anywhere/54506)._