-
-
Notifications
You must be signed in to change notification settings - Fork 78
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
Add lint declarative_macro_missing
#966
Conversation
Not sure how to address the beta failure...
|
It might need a `cargo update` to pick up the latest schema.
…On Sun, Oct 13, 2024, 9:03 AM Miikka Koskinen ***@***.***> wrote:
Not sure how to address the beta failure...
The referenced type does not exist in the schema: Macro
—
Reply to this email directly, view it on GitHub
<#966 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAR5MSTXYPY4FW77VUXYJW3Z3ILMZAVCNFSM6AAAAABPWUUBI2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBYHA2TGOBRGI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
I tried |
Hmm interesting, I might have messed something up then. I'll take a look
when I get back home later this week, sorry about that.
…On Sun, Oct 13, 2024, 10:18 AM Miikka Koskinen ***@***.***> wrote:
I tried cargo update and it didn't help. I assume the point would be to
update the versions of trustfall-rustdoc-adapter? It didn't touch the
versions of any of those.
—
Reply to this email directly, view it on GitHub
<#966 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAR5MSQAXNS7RGUUQBBFZB3Z3IUELAVCNFSM6AAAAABPWUUBI2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBYHA3TQNRVGE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
My bad, I got everything ready then just failed to cut the release 🙈 I'll have a new release up momentarily, and I'll take care of updating your PR to merge it to so I can atone for sending you down a debugging rabbit hole unnecessarily... Excellent catch on re-exporting macros as well! To my surprise, re-exporting does seem to work: playground #[macro_export]
macro_rules! inner_pub_use_will_be_removed {
() => {};
}
pub mod inner {
/// We can re-export macros at non-root paths, watch:
/// ` ``rust
/// use playground::inner::inner_pub_use_will_be_removed;
///
/// inner_pub_use_will_be_removed! {}
/// ` ``
pub use crate::inner_pub_use_will_be_removed;
} I've opened #968 to track this issue, which you are also welcome to grab if you're interested! |
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 for putting this together, and for the great ideas on how to test macros further!
Accepting with minor tweaks, which I'll apply since I feel bad for making you debug why the macro queries weren't working 😅
"zero": 0, | ||
"true": true, | ||
}, | ||
error_message: "A publicly-visible `macro_rules` declarative macro cannot be imported by its prior name. A `#[macro_export]` may have been removed, or the macro itself may have been renamed or removed entirely.", |
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.
Excellent diagnostic, I forgot that removing #[macro_export]
is a way to cause breakage here! 🎉
885d709
to
6d540ee
Compare
The v33 rustdoc JSON adapter release was also broken due to a failure of my release automation. Whew, thank goodness for good CI that prevented the merge, or else it would have been a prod break 😅 |
Working to implement the first item in #946: "removing a declarative macro that used to exist".
There's this case as well, but I'm not sure if it can be currently queried for: