# Are these type aliases actually deprecated? **URL:** \ **Category:** Discussion\ **Created:** [July 24, 2023, 8:15pm UTC](https://forums.swift.org/t/are-these-type-aliases-actually-deprecated/66336 "2023-07-24T20:15:08Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![1-877-547-7272](https://avatars.discourse-cdn.com/v4/letter/1/278dde/32.png) [@1-877-547-7272](https://forums.swift.org/u/1-877-547-7272)\ **Post date:** [July 31, 2023, 10:52pm UTC](https://forums.swift.org/t/are-these-type-aliases-actually-deprecated/66336/4 "2023-07-31T22:52:46Z")
According to [“Addressing unimplemented evolution proposals”](https://forums.swift.org/t/addressing-unimplemented-evolution-proposals/40322): > [@Addressing unimplemented evolution proposals](https://forums.swift.org/t/addressing-unimplemented-evolution-proposals/40322/1): > > Proposals which are partially implemented [within one year of acceptance] will have a "shrink to fit" approach applied, where the unimplemented parts will be removed from the proposal. I think this means that the type aliases are not deprecated, and that there is an error in the documentation. If we wanted to deprecate them, we’d have to make a new proposal. @ben-cohen is this correct? (Interestingly, that post does mention SE-0163, albeit a different part of the proposal.) --- _[View the full topic](https://forums.swift.org/t/are-these-type-aliases-actually-deprecated/66336)._