# Hide long types in error output for better readability

**URL:** <https://discourse.julialang.org/t/hide-long-types-in-error-output-for-better-readability/32104>\
**Category:** Internals & Design\
**Tags:** question, proposal, error\
**Created:** [December 10, 2019, 4:10pm UTC](https://discourse.julialang.org/t/hide-long-types-in-error-output-for-better-readability/32104 "2019-12-10T16:10:07Z")\
**Posts on this page:** 1\
**Showing post:** 20

<div class="post-metadata">

**Author:** ![sairus7](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/sairus7/32/10816_2.png) [@sairus7](https://discourse.julialang.org/u/sairus7)\
**Post date:** [February 5, 2020, 9:19am UTC](https://discourse.julialang.org/t/hide-long-types-in-error-output-for-better-readability/32104/20 "2020-02-05T09:19:28Z")

</div>

There are two parts of long type strings:

- Deeply nestred parametric types (with a lot of `{}` braces).
- Long type names for each individual type (like `QueryOperators.GroupColumnArrayView`).

For some standard types like arrays or tuples there was a proposal to change their names to a shorter syntax in declarations:

> [@Short type declarations (syntax sugar)?](https://discourse.julialang.org/t/short-type-declarations-syntax-sugar/26114/7):
>
> Thanks for the interesting historical tangent! In this context, I have to ask: Why did we decide against {T1,T2} as a shorthand for Tuple{T1,T2}? Very naively, this syntax looks free (Error: syntax: { } vector syntax is discontinued), natural, and the current Tuple{...} is pretty verbose.

---

_[View the full topic](https://discourse.julialang.org/t/hide-long-types-in-error-output-for-better-readability/32104)._