Pre-RFC: allow conflicting names on import, only complain if used ambiguously

What about using S as a function?

RFC 1560 and RFC 1422 tried hard to avoid treating private imports specially, it feels entirely wrong to me to introduce such a special treatment now. @jseyfried also described what complications arise when we try to avoid reexporting "ambiguity items".

Using S as a function would similarly produce an error about the conflicting versions of S.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.