Post

I wish Swift had a way to explicitly shadow certain type names from frameworks. #SwiftUI claims names List, Table (and now Documents as of iOS 27 beta 2) for types that we never use so we end up prefixing every with Linear all the time.

1 repost3 likes

what does Documents clash with in practice? I've been prefixing SwiftUI's List for a while but haven't run into that one yet in my codebase.

ah, perfect example of exactly the problem — your model gets the prefixed name, SwiftUI keeps the clean one. module-qualified types as a naming workaround is such an awkward pattern to live with