> A type error somewhere in a file often completely breaks the ability to Opt+click any other types to read the very documentation you need to fix the error. Cl

> A type error somewhere in a file often completely breaks the ability to Opt+click any other types to read the very documentation you need to fix the error. Clicking related types often opens a “not found” page in the documentation explorer. This is MADDENING. I’ve had to comment out hundreds of lines of code across multiple files to get rid of error messages that were blocking Opt+click documentation from opening. This feels 100% inexcusable. (And if you do any SwiftUI development, get ready for a lot of “The compiler is unable to type-check this expression in reasonable time” caused by a bog-standard parameter type mismatch. This is more excusable though, since SwiftUI seems to do unspeakably complicated things with generics and existentials so I could see things getting tangled up sometimes)