# 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\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![StefanKarpinski](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stefankarpinski/32/24_2.png) [@StefanKarpinski](https://discourse.julialang.org/u/StefanKarpinski)\
**Post date:** [February 3, 2023, 10:47pm UTC](https://discourse.julialang.org/t/rfc-add-a-type-called-anytype-thats-subtyped-by-all-other-types-except-any/93956/11 "2023-02-03T22:47:10Z")

</div>

> [@Sukera](#):
>
> This is only complicated by the fact that we now CANNOT remove that behavior until a breaking version in julia itself is introduced.

I disagree with that position. The fact that you can pass a non-type to a parametric type that explicitly has a `<: Any` declaration on that type parameter is a bug plain and simple (and not one that has anything to do with grammar or syntax). If there’s code that breaks when that bug gets fixed then so be it—that code has to be fixed. Semantic versioning does not mean we can’t make any changes that change the behavior of any code anywhere. It means we can’t make breaking changes to documented and intentional APIs which I don’t believe this to be.

---

_[View the full topic](https://discourse.julialang.org/t/rfc-add-a-type-called-anytype-thats-subtyped-by-all-other-types-except-any/93956)._