-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
Resolve: stop trying to resolve an import directive after the resolution fails #31747
Conversation
…efactor away `resolved_import_count`
@bors: r+ |
📌 Commit 5ad84f1 has been approved by |
⌛ Testing commit 5ad84f1 with merge fff06cb... |
@bors: retry force |
⌛ Testing commit 5ad84f1 with merge ead67e7... |
💔 Test failed - auto-linux-32-opt |
@bors: retry On Fri, Feb 19, 2016 at 11:39 AM, bors notifications@github.com wrote:
|
Now that #31461 is merged, a failing resolution can never become indeterminate or succeed, so we no longer have to keep trying to resolve failing import directives.
r? @nrc