Some types appear in quinn's public API which are not accessible through quinn directly

[gretchenfrage]

One example of this was noted in #1757:

• quinn does not re-export quinn_proto::TransportError and other downstream-API-exposed types despite that being a public part of quinn's API via quinn's re-exporting of quinn_proto::ConnectionError

Another example is that StreamId's public API involves Side and Dir, but Side and Dir cannot be referenced without adding quinn_proto in addition to quinn as a dependency.

If this is indeed something we wish to avoid, it would be nice to have some automated tool which could detect such cases.

[djc]

We generally want to fix these. Don't know that automated tools for this exist?

[gretchenfrage]

Yes, I wasn't aware of one existing and at a cursory glance I didn't find one. Which seems a bit odd given how useful and not-that-hard this seems.