# Pitch: Key-Path Member Lookup

**URL:** <https://forums.swift.org/t/pitch-key-path-member-lookup/21579>\
**Category:** Pitches\
**Created:** [March 13, 2019, 10:26pm UTC](https://forums.swift.org/t/pitch-key-path-member-lookup/21579 "2019-03-13T22:26:17Z")\
**Posts on this page:** 1\
**Showing post:** 68

<div class="post-metadata">

**Author:** ![xwu](https://avatars.discourse-cdn.com/v4/letter/x/b487fb/32.png) [@xwu](https://forums.swift.org/u/xwu)\
**Post date:** [March 25, 2019, 3:41am UTC](https://forums.swift.org/t/pitch-key-path-member-lookup/21579/68 "2019-03-25T03:41:43Z")

</div>

> [@anandabits](#):
>
> This is an interesting example, thanks for sharing it! I can see more clearly what you’re getting at now.

Sure; as another example, consider @scanon's thoughts about swizzling for SIMD types here:

> [@SE-0251: SIMD Additions](https://forums.swift.org/t/se-0251-simd-additions/21957/15):
>
> We could also wrap that in some compilerEvaluable + dynamicMemberLookup at some future point to actually allow `v.xxyz` if we wanted to.

Point being, it is not the case that `@dynamicMemberLookup` means no static checking. In fact, anticipate that there will be static checking where it makes sense, when it becomes possible to do so.

---

_[View the full topic](https://forums.swift.org/t/pitch-key-path-member-lookup/21579)._