# Displaying complex version of numeric type

**URL:** <https://discourse.julialang.org/t/displaying-complex-version-of-numeric-type/11016>\
**Category:** General Usage\
**Created:** [May 19, 2018, 5:56pm UTC](https://discourse.julialang.org/t/displaying-complex-version-of-numeric-type/11016 "2018-05-19T17:56:33Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![Ralph\_Smith](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ralph_smith/32/10344_2.png) [@Ralph\_Smith](https://discourse.julialang.org/u/Ralph_Smith)\
**Post date:** [May 20, 2018, 4:24pm UTC](https://discourse.julialang.org/t/displaying-complex-version-of-numeric-type/11016/9 "2018-05-20T16:24:31Z")

</div>

I agree that well-defined and documented interfaces, with infrastructure that enforces them, would be better than workarounds such as I described. But all this takes work, and people keep finding reasons to give higher priority to other matters.

With regard to traits etc., I’ll point to [this thread on multiple traits](https://discourse.julialang.org/t/why-does-julia-not-support-multiple-traits/5278) as evidence that some of the developers (a) recognize these issues to be important and (b) understand that a good solution is likely to be difficult.

---

_[View the full topic](https://discourse.julialang.org/t/displaying-complex-version-of-numeric-type/11016)._