You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With latest rust getting lots of ambiguous re-export errors, I think introduces here: rust-lang/rust#109538 for v1.70.0
It sounds like when same type names are re-exported (like DeleteError which is exported in multiple graphql definitions).
Do we silence it ? Or do we amend exports ? I would assume when those types are used they are qualified (use SomeType; SomeType::DeleteError) with full name rather then imported, so should be pretty easy to remove the re-export ?
I think it's glob exports, so pub(crate) them ?
The text was updated successfully, but these errors were encountered:
With latest rust getting lots of ambiguous re-export errors, I think introduces here: rust-lang/rust#109538 for v1.70.0
It sounds like when same type names are re-exported (like DeleteError which is exported in multiple graphql definitions).
Do we silence it ? Or do we amend exports ? I would assume when those types are used they are qualified (
use SomeType; SomeType::DeleteError
) with full name rather then imported, so should be pretty easy to remove the re-export ?I think it's glob exports, so pub(crate) them ?
The text was updated successfully, but these errors were encountered: