-
Notifications
You must be signed in to change notification settings - Fork 356
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
Confusing elided-lifetimes-in-paths lint in bridge #907
Comments
Ahhhh, I see what it's trying to indicate now. It's complaining about the generated |
I'm running into the same issue and wondering if there is any workaround for this? @sbrocket |
I am not a fan of this lint and I don't think codebases should use it, but I've published support for it in 1.0.60. |
Thanks for the fix. I’m not a fan of the lint either, but it’s grouped in `
rust_2018_idioms` and we get it from there, so it fits someone’s definition
of “idiomatic” 2018 edition usage.
…On Fri, Dec 10, 2021 at 1:39 PM David Tolnay ***@***.***> wrote:
I am not a fan of this lint and I don't think codebases should use it, but
I've published support for it in 1.0.60.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#907 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAEIBAN6JWAP3LEL2UCW2LUQJXP7ANCNFSM5BNVQRJA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Building the demo with
-W elided-lifetimes-in-paths
results in the following:However, neither
cxx::UniquePtr
norBlobstoreClient
have a lifetime parameter, so of course trying to add one is an error (and of course the lint still triggers too):Looking at the expanded output with
cargo expand
, I don't see any clues as to what missing anonymous lifetime the compiler might be intending to flag here. It's unclear to me if this is a lint bug, if the compiler diagnostic is just confusing due to thecxx::bridge
proc macro, or something else.This is an issue for us because our codebase uses both
-W rust_2018_idioms
and-D warnings
by default. Worse,elided-lifetimes-in-paths
can only be allowed at the crate level (rust-lang/rust#71957) so we can't just allow it for thecxx::bridge
module.The text was updated successfully, but these errors were encountered: