It's not a 100% valid workaround because now you're relying on the unqualified types always having the same behavior even if your dependencies change. I don't foresee any problems if you ship that way today, but one of the goals of module interfaces is to work with next year's Swift and next year's dependent libraries, and that only applies to module interfaces as generated from the compiler.
1 Like