# How to understand Traceur's output?

**URL:** <https://discourse.julialang.org/t/how-to-understand-traceurs-output/25191>\
**Category:** General Usage\
**Tags:** question\
**Created:** [June 12, 2019, 12:45pm UTC](https://discourse.julialang.org/t/how-to-understand-traceurs-output/25191 "2019-06-12T12:45:20Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![tim-oh](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tim-oh/32/8410_2.png) [@tim-oh](https://discourse.julialang.org/u/tim-oh)\
**Post date:** [June 12, 2019, 10:48pm UTC](https://discourse.julialang.org/t/how-to-understand-traceurs-output/25191/2 "2019-06-12T22:48:04Z")

</div>

Same for me. At least for newcomers it’s hard to understand what and where the issue is. It’d be so cool if it could point to the offending line in the code, stacktrace style, and to the relevant performance tips section… not a complaint, Traceur is great and I’m sure that it’ll all become more obvious as we learn from our mistakes. I just wish it shoved my nose into the mess and shouted out what I did wrong.

EDIT:  
Looking at the [announcement](https://discourse.julialang.org/t/ann-traceur-jl-make-your-julia-code-not-totally-slow/9469), the output shown there does look a lot like what I was wishing for, whereas mine is like cserteGT3’s. Should @trace be run in the REPL, have other things changed (e.g. some people point out that @code\_warntype output used to be more easily legible) or am I making a mistake?

---

_[View the full topic](https://discourse.julialang.org/t/how-to-understand-traceurs-output/25191)._