-
Notifications
You must be signed in to change notification settings - Fork 1
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
Apply assure
and forward
directly to expressions
#37
Comments
Unfortunately this restriction has only been lifted for function-like proc-macros. pre uses attribute proc-macros, where this restriction still applies. The following code still fails on 1.45 fn main() {
unsafe {
#[test_macro]
foo()
}
} with this error message
I guess this issue could be left open though, until that limitation can be lifted. |
assure
and forward
directly to expressions
Ergh, I obviously misunderstood the situation. Thanks for the patient response. :) |
No worries, I had to double check as well, when I read the patch notes. |
Rust 1.45 lifts the restriction that proc-macros cannot be invoked in expression and statement position, which is the restriction referred to as the reason for needing a#[pre]
macro on items using#[assure(...)]
in the latest (0.2.0) crate docs:What are plans for this crate now that this restriction has been lifted? Is any help needed to, say, lift the constraint that#[pre]
needs to be applied to items?The premise of the question is invalid, but @aticu has left this issue open and renamed it appropriately.
The text was updated successfully, but these errors were encountered: