# \[ANN\] SimpleTypePrint.jl: customize how types are displayed

**URL:** <https://discourse.julialang.org/t/ann-simpletypeprint-jl-customize-how-types-are-displayed/52115>\
**Category:** Package Announcements\
**Tags:** announcement\
**Created:** [December 20, 2020, 5:26am UTC](https://discourse.julialang.org/t/ann-simpletypeprint-jl-customize-how-types-are-displayed/52115 "2020-12-20T05:26:02Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![mcabbott](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mcabbott/32/6603_2.png) [@mcabbott](https://discourse.julialang.org/u/mcabbott)\
**Post date:** [December 21, 2020, 6:57pm UTC](https://discourse.julialang.org/t/ann-simpletypeprint-jl-customize-how-types-are-displayed/52115/9 "2020-12-21T18:57:49Z")

</div>

For stack traces, there is a function `print_type_stacktrace` which handles the colour printing of types. Overloading that to shorten things doesn’t seem likely to break anything else, and might be worth doing in general. Also discussed a bit in [this thread](https://discourse.julialang.org/t/these-stack-traces-are-out-of-control/47162). (Edit – maybe this is the issue: [https://github.com/JuliaLang/julia/issues/36517](https://github.com/JuliaLang/julia/issues/36517) .)

I don’t think that would affect method error printing. It would be nice if that could be abbreviated to enough levels to show the mismatch, somehow. If `f` only accepts some particular kind of AbstractArray, and I call it with a tuple (of complicated objects), then the mismatch is at the outermost layer.

---

_[View the full topic](https://discourse.julialang.org/t/ann-simpletypeprint-jl-customize-how-types-are-displayed/52115)._