fix(resolve): update the ambiguity glob binding as warning recursively#113099
fix(resolve): update the ambiguity glob binding as warning recursively#113099bors merged 2 commits intorust-lang:masterfrom
Conversation
|
r? @TaKO8Ki (rustbot has picked a reviewer for you, use r? to override) |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
Meta: not sure why new PR, we could continue in #112743, but it's fine too. |
Ahh, just because I feel there are some differences in the way they are implemented, perhaps the new PR can provide a clearer message. Of course, this matter is not important, and we don't need to dwell on it. |
|
Could you also move all the new tests from |
This comment was marked as resolved.
This comment was marked as resolved.
This comment has been minimized.
This comment has been minimized.
This comment was marked as resolved.
This comment was marked as resolved.
|
I have added @rustbot ready |
|
@bors r+ |
|
☀️ Test successful - checks-actions |
|
As the next step, I will attempt to address the issue at #113834. |
|
Finished benchmarking commit (2dc6610): comparison URL. Overall result: ❌ regressions - ACTION NEEDEDNext Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 650.158s -> 652.195s (0.31%) |
|
Minor regressions for @rustbot label: +perf-regression-triaged |
| Warn, | ||
| "detects certain glob imports that require reporting an ambiguity error", | ||
| @future_incompatible = FutureIncompatibleInfo { | ||
| reason: FutureIncompatibilityReason::FutureReleaseError, |
There was a problem hiding this comment.
FWIW this FutureIncompatibilityReason will make the warning only show up in locally built crates, but not in cargo's future breakage report that also shows warnings from dependencies. Just making sure that this is a deliberate choice and not an accident. :)
There was a problem hiding this comment.
I just assumed all future incompatibility lints are reported for dependencies during review.
There was a problem hiding this comment.
No, that's not the case. #116049 should help clarify (but doesn't change the behavior of any existing lint).
| // However we currently using `Some(old_binding)` for back compact | ||
| // purposes. | ||
| // This case can be removed after once `Undetermined` is prepared | ||
| // for glob-imports. |
There was a problem hiding this comment.
Sigh, this case was supposed to produce ambiguous_glob_imports lint for years, but it never did, so we cannot remove it now.
I've noticed it just now...
Fixes #47525
Fixes #56593, but
issue-56593-2.rsis not fixed to ensure backward compatibility.Fixes #98467
Fixes #105235
Fixes #112713
This PR had added a field called
warn_ambiguousinNameBindingwhich is only for back compatibly reason and used for lint.More details: #112743
r? @petrochenkov