# Key Path inference and diagnostic improvements - An Update

**URL:** <https://forums.swift.org/t/key-path-inference-and-diagnostic-improvements-an-update/69632>\
**Category:** Compiler\
**Tags:** gsoc-2023\
**Created:** [January 25, 2024, 9:03pm UTC](https://forums.swift.org/t/key-path-inference-and-diagnostic-improvements-an-update/69632 "2024-01-25T21:03:38Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![KeithBauerANZ](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/keithbaueranz/32/27897_2.png) [@KeithBauerANZ](https://forums.swift.org/u/KeithBauerANZ)\
**Post date:** [January 25, 2024, 9:45pm UTC](https://forums.swift.org/t/key-path-inference-and-diagnostic-improvements-an-update/69632/2 "2024-01-25T21:45:21Z")

</div>

I wonder if this breaks [BrainF\*\*\* in the Swift type system](https://forums.swift.org/t/brainf-in-the-swift-type-system/68301/1), which relies heavily on type inference for KeyPaths being able to do an unbounded search!

(I don't mind if it does, and I doubt it'd break much if any "real" code, but it'd be funny if this technique was disallowed immediately after I discovered it)

---

_[View the full topic](https://forums.swift.org/t/key-path-inference-and-diagnostic-improvements-an-update/69632)._
