# Improving the UI of generics

**URL:** <https://forums.swift.org/t/improving-the-ui-of-generics/22814>\
**Category:** Discussion\
**Created:** [April 8, 2019, 3:48pm UTC](https://forums.swift.org/t/improving-the-ui-of-generics/22814 "2019-04-08T15:48:05Z")\
**Posts on this page:** 1\
**Showing post:** 92

<div class="post-metadata">

**Author:** ![DevAndArtist](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/devandartist/32/287_2.png) [@DevAndArtist](https://forums.swift.org/u/DevAndArtist)\
**Post date:** [April 13, 2019, 6:37am UTC](https://forums.swift.org/t/improving-the-ui-of-generics/22814/92 "2019-04-13T06:37:32Z")

</div>

I think you did a correct observation here, even if we had `Meta<T>`, it would probably be a generic keyword type similar to non-generic Any as keyword type. That implies it won‘t be a citizen of stdlib directly.

My conclusion is:

- I hope we can move away from `T.Type` and reclaim `.Type`
- With this we could clean up metatypes drastically.
- We would communicate their behavior more clearly.
- We would get a new set of constraints we could express in Swift‘s type sytem.

---

_[View the full topic](https://forums.swift.org/t/improving-the-ui-of-generics/22814)._