Hello Swift community, I did a quick research and found almost zero input for this topic:
I myself always wondered why
@testable, described as a hack in the first link above, can only allow testing
internal members. Since we already moved to a soft
private access modifier it won’t make much sense to extend
How hard would it be for someone to implement this feature and to allow testing all members of a module (
internal, and the new ones
I think the proposal for that feature isn’t much of a problem, but the implementation for the review process is. If we can find someone who is willing to tackle the implementation and maybe is capable to provide the first version fairly fast, I think we could push this feature forward very fast and benefit from it in Swift 5.