-
Notifications
You must be signed in to change notification settings - Fork 148
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
Flag misinterpreted as option when using macros on Rust 1.47.0 #439
Comments
This can be further simplified to macro_rules! m {
($bool:ty) => {
#[derive(Debug, StructOpt)]
struct Opts {
#[structopt(long = "x")]
x: $bool
}
};
}
m!(bool); Basically, tokens passed to a macro and assigned to a metavariable ( |
CreepySkeleton
added a commit
that referenced
this issue
Oct 12, 2020
Merged
CreepySkeleton
added a commit
that referenced
this issue
Oct 12, 2020
CreepySkeleton
added a commit
that referenced
this issue
Oct 12, 2020
This was referenced Mar 12, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It seems that with 1.47.0 macro'ing structopt causes misbehavior in the functionality of structopt. I found out that a flag gets erroneously parsed as an option instead.
In this example:
when compiling with Rust 1.46.0
with Rust 1.47.0
I believe that it might be because of rust-lang/rust#73084
The text was updated successfully, but these errors were encountered: