# Why does Swift so often fail to find symbols?

**URL:** <https://forums.swift.org/t/why-does-swift-so-often-fail-to-find-symbols/54709>\
**Category:** Using Swift\
**Created:** [January 19, 2022, 1:38am UTC](https://forums.swift.org/t/why-does-swift-so-often-fail-to-find-symbols/54709 "2022-01-19T01:38:42Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![eskimo](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/eskimo/32/13558_2.png) [@eskimo](https://forums.swift.org/u/eskimo)\
**Post date:** [January 19, 2022, 9:16am UTC](https://forums.swift.org/t/why-does-swift-so-often-fail-to-find-symbols/54709/3 "2022-01-19T09:16:30Z")

</div>

> maybe it's a definition the clang importer cannot parse.

Speaking of which, there’s progress on that front, to wit, [Lazy ClangImporter Diagnostics Enabled by Default](https://forums.swift.org/t/pitch-lazy-clangimporter-diagnostics-enabled-by-default/54651). Yay!

Share and Enjoy

Quinn “The Eskimo!” @ DTS @ Apple

---

_[View the full topic](https://forums.swift.org/t/why-does-swift-so-often-fail-to-find-symbols/54709)._