# RFC: add a Type called AnyType that's subtyped by all other types except Any

**URL:** <https://discourse.julialang.org/t/rfc-add-a-type-called-anytype-thats-subtyped-by-all-other-types-except-any/93956>\
**Category:** Internals & Design\
**Tags:** proposal, type, dispatch, rfc\
**Created:** [February 2, 2023, 10:52pm UTC](https://discourse.julialang.org/t/rfc-add-a-type-called-anytype-thats-subtyped-by-all-other-types-except-any/93956 "2023-02-02T22:52:48Z")\
**Posts on this page:** 1\
**Page:** 2

<div class="post-metadata">

**Author:** ![frankwswang](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/frankwswang/32/18561_2.png) [@frankwswang](https://discourse.julialang.org/u/frankwswang)\
**Post date:** [October 26, 2023, 11:38pm UTC](https://discourse.julialang.org/t/rfc-add-a-type-called-anytype-thats-subtyped-by-all-other-types-except-any/93956/21 "2023-10-26T23:38:58Z")

</div>

Thanks for the explanation! Sorry for the late reply! I’m not professionally trained in PL and type theories, so I needed to think about this more… Based on my personal experiences with Julia’s package development, I think the current type system has already put a considerable burden on the compiler when doing type inference for complicated composite types (e.g., overspecialization). We should be more cautious when considering any future modifications to the system. I do hope there’s a solution that can be implemented when the time is right.

[Previous page](https://discourse.julialang.org/t/rfc-add-a-type-called-anytype-thats-subtyped-by-all-other-types-except-any/93956.md?page=1)