-
Notifications
You must be signed in to change notification settings - Fork 12.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
regression: read_to_string import error #82670
Comments
This is not a resolver change, but a library addition of Resolver tries pretty hard to resolve ambiguities like this arising from library additions (e.g. single import wins over glob import, two glob imports do not conflict unless the ambiguous name is actually used), but in case of two glob imports and an actually used ambiguous name we truly cannot do anything. Addition of any new item to any library has a potential to cause breakage like this, so it is considered an acceptable breakage. |
Sounds good. I missed that merged in 1.51, re-tagging libs. |
Triage: Closing this as an acceptable breakage. |
I suspect this is a change in behavior for the resolver, cc @petrochenkov -- probably fixing a bug in practice, but in case it was unintentional seems good to flag.
The text was updated successfully, but these errors were encountered: