-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Handle more cases in cfg_accessible #97391
Conversation
806b00c
to
bc049c1
Compare
This comment has been minimized.
This comment has been minimized.
I've address the review comments. This is ready for another review. @rustbot ready |
fc9dc1a
to
a6156ca
Compare
I've addressed all review comments expect #97391 (comment) for which I put a message describing the situation. @rustbot ready |
This comment has been minimized.
This comment has been minimized.
I've addressed the review comments: removed @rustbot ready |
trait TraitAlias = std::fmt::Debug + Send; | ||
|
||
// FIXME: Currently shows "cannot determine" but should be `false` | ||
#[cfg_accessible(unresolved)] //~ ERROR cannot determine |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not a bug, if the compiler says "cannot determine" (rather than "not sure") then it's legitimately stuck, and it's unlikely we can do anything here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The problem here is that we return an error instead of false
(ie it is unresolvable).
The error message is irrelevant to the bug.
I've reverted the @rustbot ready |
Thanks! |
📌 Commit b76d112 has been approved by |
☀️ Test successful - checks-actions |
Finished benchmarking commit (656eec8): comparison url. Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)Results
CyclesResults
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression Footnotes |
This PR tries to handle more cases in the cfg_accessible implementation by only emitting a "not sure" error only if we have partially resolved a path.
This PR also adds many tests for the "not sure" cases and for private items.
r? @petrochenkov