The hidden cost of @testable

Swift's @testable annotation affects how a module is imported, changing its access control to simplify testing. In this interesting post, Paul Samuels argues that there are hidden costs to using this feature. I don't entirely agree with everything Paul states, but it's always good to consider a different point of view.