Double-underscored methods revealed in autocomplete using @testable imports

Are testable imports supposed to make double-underscored private methods visible in autocomplete? I wasn't sure if this was intended to let test writers more easily check the behaviour of things like derived conformances, or if this is a bug. I think it's the latter? I searched and found this, which is related to access control of the derived enum method, but not clear if it fully covers the same issue.

@jrose does this look like the same issue to you?

@testable should only expose internal members, but since @testable is nothing than a dirty compiler hack, I think you discovered a bug here. Would you mind to report it?

In this thread I discussed the attribute a while ago:

I don’t think so. @bzamayo, can you please file this separately?

Will do. Thanks for checking Jordan.