Prevent explicitly specifiying lifetime arguments to functions when the parameters are not visible in the type signature. - #160581
Prevent explicitly specifiying lifetime arguments to functions when the parameters are not visible in the type signature.#160581addiesh wants to merge 1 commit into
Conversation
…he parameters are not visible in the type signature.
|
HIR ty lowering was modified cc @fmease |
|
Thanks for the pull request, and welcome! The Rust Project is excited to review your changes, and you should hear from @mejrs (or someone else) some time within the next two weeks. Please see the contribution instructions for more information. Namely, in order to ensure the minimum review times lag, PR authors and assigned reviewers should ensure that the review label (
Why was this reviewer chosen?The reviewer was selected based on:
|
|
Isn't this a breaking change? |
|
I don't think so? Afaik, the only way that this can happen is through a bug. It may be worth a crater run to check to see if anyone is relying on this behavior though? |
|
Well, that depends on how breaking it is :) |
This comment has been minimized.
This comment has been minimized.
|
@bors try |
This comment has been minimized.
This comment has been minimized.
Prevent explicitly specifiying lifetime arguments to functions when the parameters are not visible in the type signature.
|
@craterbot check |
|
👌 Experiment ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
This is meant to fix #154490:
This started as a larger PR (#160471) but these changes work on their own.
Eventually, that PR should introduce the same checks for late-bound lifetimes.