-
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
Do precise capturing arg validation in resolve #130414
Do precise capturing arg validation in resolve #130414
Conversation
Some changes occurred in diagnostic error codes |
This comment has been minimized.
This comment has been minimized.
a9617b4
to
10af205
Compare
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.
Thanks, these diagnostics look much more helpful 👍
Please r=me after fixing the typo in error code docs since I think those are user-facing. |
10af205
to
ae8b460
Compare
@bors r=jieyouxu |
☀️ Test successful - checks-actions |
Finished benchmarking commit (3a22be3): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)This benchmark run did not return any relevant results for this metric. CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 759.454s -> 758.941s (-0.07%) |
Moves the validation of precise capturing args (
use<T, N>
) out ofresolve_bound_vars
and intorustc_resolve
. This both simplifies the impl and fixes a bug when we haveuse<arg>
wherearg
is one of the function args.This also introduces new error codes specifically for precise capturing, to avoid reusing the other error codes which are not as accurate.
Fixes #130399