Skip to content
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

Future incompatibility warning because of dependency on nom 1.2.4 #4

Open
mtkennerly opened this issue Mar 16, 2023 · 0 comments
Open

Comments

@mtkennerly
Copy link

Using Rust 1.68.0, this warning is displayed while building:

warning: the following packages contain code that will be rejected by a future version of Rust: nom v1.2.4

Sample reason:

$ cargo report future-incompatibilities --id 359 --package [email protected]
> warning: trailing semicolon in macro used in expression position
>    --> C:\Users\mtken\.cargo\registry\src\github.com-1ecc6299db9ec823\nom-1.2.4\src\macros.rs:482:40
>     |
> 482 |     map_impl!($i, call!($f), call!($g));
>     |                                        ^
>     |
>    ::: C:\Users\mtken\.cargo\registry\src\github.com-1ecc6299db9ec823\nom-1.2.4\src\nom.rs:329:3
>     |
> 329 |   map!(i, be_u8, | x | { x as i8 })
>     |   --------------------------------- in this macro invocation
>     |
>     = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
>     = note: for more information, see issue #79813 <https://github.com/rust-lang/rust/issues/79813>
>     = note: macro invocations at the end of a block are treated as expressions
>     = note: to ignore the value produced by the macro, add a semicolon after the invocation of `map`
>     = note: `#[allow(semicolon_in_expressions_from_macros)]` on by default
>     = note: this warning originates in the macro `map` (in Nightly builds, run with -Z macro-backtrace for more info)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant