# What is difference between Type{T} and T

**URL:** <https://discourse.julialang.org/t/what-is-difference-between-type-t-and-t/19325>\
**Category:** New to Julia\
**Tags:** type, parametric-types\
**Created:** [January 6, 2019, 3:42pm UTC](https://discourse.julialang.org/t/what-is-difference-between-type-t-and-t/19325 "2019-01-06T15:42:15Z")\
**Posts on this page:** 1\
**Showing post:** 52

<div class="post-metadata">

**Author:** ![Henrique\_Becker](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/henrique_becker/32/15443_2.png) [@Henrique\_Becker](https://discourse.julialang.org/u/Henrique_Becker)\
**Post date:** [March 13, 2021, 7:04pm UTC](https://discourse.julialang.org/t/what-is-difference-between-type-t-and-t/19325/52 "2021-03-13T19:04:52Z")

</div>

I do not know if this was already cited. But on [another recent thread](https://discourse.julialang.org/t/weird-tuple-types-that-seem-like-they-should-be-disallowed/57080/1) the [issue #29368 redesign typeof(::Type)](https://github.com/JuliaLang/julia/issues/29368#) was mentioned, and right on the original post:

> A related issue is that types like `DataType` and `Type{Int}` have an overly-complex subtype and specificity relationship: one is not a subtype of the other, but their intersection is non-empty, _and_ we’re not able to accurately represent that intersection. For various reasons (including backwards compatibility) subtyping currently gets this wrong on purpose, making `Type{Int} <: DataType` true.

---

_[View the full topic](https://discourse.julialang.org/t/what-is-difference-between-type-t-and-t/19325)._