A fix has to be implemented by those dependencies

I built a program using below dependencies:

[dependencies]
calamine = "0.23.1"
xlsxwriter = "0.1.0"
csv = "1.1"

At the end, cargo tells me this:

cargo build --release --future-incompat-report
Finished release [optimized] target(s) in 4.10s
warning: the following packages contain code that will be rejected by a future version of Rust: cexpr v0.3.6, nom v4.2.3
note:
To solve this problem, you can try the following approaches:

• Some affected dependencies have newer versions available.
  You may want to consider updating them to a newer version to see if the issue has been fixed.

cexpr v0.3.6 has the following newer versions available: 0.4.0, 0.5.0, 0.6.0
nom v4.2.3 has the following newer versions available: 5.0.0-alpha1, 5.0.0-alpha2, 5.0.0-beta1, 5.0.0-beta2, 5.0.0-beta3, 5.0.0, 5.0.1, 5.1.0, 5.1.1, 5.1.2, 5.1.3, 6.0.0-alpha1, 6.0.0-alpha2, 6.0.0-alpha3, 6.0.0-beta1, 6.0.0-beta2, 6.0.0-beta3, 6.0.0-beta4, 6.0.0-beta5, 6.0.0, 6.0.1, 6.1.0, 6.1.1, 6.1.2, 6.2.0, 6.2.1, 6.2.2, 7.0.0-alpha1, 7.0.0-alpha2, 7.0.0-alpha3, 7.0.0, 7.1.0, 7.1.1, 7.1.2, 7.1.3

• If the issue is not solved by updating the dependencies, a fix has to be
  implemented by those dependencies. You can help with that by notifying the
  maintainers of this problem (e.g. by creating a bug report) or by proposing a
  fix to the maintainers (e.g. by creating a pull request):

  • cexpr@0.3.6
  • Repository: https://github.com/jethrogb/rust-cexpr
  • Detailed warning command: cargo report future-incompatibilities --id 1 --package cexpr@0.3.6

The result of previous command is:

The following warnings were discovered during the build. These warnings are an
indication that the packages contain code that will become an error in a
future release of Rust. These warnings typically cover changes to close
soundness problems, unintended or undocumented behavior, or critical problems
that cannot be fixed in a backwards-compatible fashion, and are not expected
to be in wide use.

Each warning should contain a link for more information on what the warning
means and how to resolve it.

To solve this problem, you can try the following approaches:

• Some affected dependencies have newer versions available.
  You may want to consider updating them to a newer version to see if the issue has been fixed.

cexpr v0.3.6 has the following newer versions available: 0.4.0, 0.5.0, 0.6.0
nom v4.2.3 has the following newer versions available: 5.0.0-alpha1, 5.0.0-alpha2, 5.0.0-beta1, 5.0.0-beta2, 5.0.0-beta3, 5.0.0, 5.0.1, 5.1.0, 5.1.1, 5.1.2, 5.1.3, 6.0.0-alpha1, 6.0.0-alpha2, 6.0.0-alpha3, 6.0.0-beta1, 6.0.0-beta2, 6.0.0-beta3, 6.0.0-beta4, 6.0.0-beta5, 6.0.0, 6.0.1, 6.1.0, 6.1.1, 6.1.2, 6.2.0, 6.2.1, 6.2.2, 7.0.0-alpha1, 7.0.0-alpha2, 7.0.0-alpha3, 7.0.0, 7.1.0, 7.1.1, 7.1.2, 7.1.3

• If the issue is not solved by updating the dependencies, a fix has to be
  implemented by those dependencies. You can help with that by notifying the
  maintainers of this problem (e.g. by creating a bug report) or by proposing a
  fix to the maintainers (e.g. by creating a pull request):

  • cexpr@0.3.6

  • Repository: https://github.com/jethrogb/rust-cexpr

  • Detailed warning command: cargo report future-incompatibilities --id 1 --package cexpr@0.3.6

  • nom@4.2.3

  • Repository: https://github.com/Geal/nom

  • Detailed warning command: cargo report future-incompatibilities --id 1 --package nom@4.2.3

• If waiting for an upstream fix is not an option, you can use the [patch]
  section in Cargo.toml to use your own version of the dependency. For more
  information, see:
  https://doc.rust-lang.org/cargo/reference/overriding-dependencies.html#the-patch-section

The package cexpr v0.3.6 currently triggers the following future incompatibility lints:

warning: trailing semicolon in macro used in expression position
--> C:\Users\huertaga.cargo\registry\src\index.crates.io-6f17d22bba15001f\cexpr-0.3.6\src\literal.rs:100:23
|
100 | full!($i, call!($f));
| ^
...
258 | / named!(one_literal<&[u8],EvalResult,::Error>,
259 | | fix_error!(::Error,alt_complete!(
260 | | map!(full!(c_char),EvalResult::Char) |
261 | | map!(full!(c_int),|i|EvalResult::Int(::std::num::Wrapping(i))) |
... |
264 | | ))
265 | | );
| |_- 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 rust-lang/rust#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 full
= note: #[allow(semicolon_in_expressions_from_macros)] on by default
= note: this warning originates in the macro full which comes from the expansion of the macro named (in Nightly builds, run with -Z macro-backtrace for more info)

warning: trailing semicolon in macro used in expression position
--> C:\Users\huertaga.cargo\registry\src\index.crates.io-6f17d22bba15001f\cexpr-0.3.6\src\literal.rs:100:23
|
100 | full!($i, call!($f));
| ^
...
258 | / named!(one_literal<&[u8],EvalResult,::Error>,
259 | | fix_error!(::Error,alt_complete!(
260 | | map!(full!(c_char),EvalResult::Char) |
261 | | map!(full!(c_int),|i|EvalResult::Int(::std::num::Wrapping(i))) |
... |
264 | | ))
265 | | );
| |_- 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 rust-lang/rust#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 full
= note: #[allow(semicolon_in_expressions_from_macros)] on by default
= note: this warning originates in the macro full which comes from the expansion of the macro named (in Nightly builds, run with -Z macro-backtrace for more info)

warning: trailing semicolon in macro used in expression position
--> C:\Users\huertaga.cargo\registry\src\index.crates.io-6f17d22bba15001f\cexpr-0.3.6\src\literal.rs:100:23
|
100 | full!($i, call!($f));
| ^
...
258 | / named!(one_literal<&[u8],EvalResult,::Error>,
259 | | fix_error!(::Error,alt_complete!(
260 | | map!(full!(c_char),EvalResult::Char) |
261 | | map!(full!(c_int),|i|EvalResult::Int(::std::num::Wrapping(i))) |
... |
264 | | ))
265 | | );
| |_- 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 rust-lang/rust#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 full
= note: #[allow(semicolon_in_expressions_from_macros)] on by default
= note: this warning originates in the macro full which comes from the expansion of the macro named (in Nightly builds, run with -Z macro-backtrace for more info)

warning: trailing semicolon in macro used in expression position
--> C:\Users\huertaga.cargo\registry\src\index.crates.io-6f17d22bba15001f\cexpr-0.3.6\src\literal.rs:100:23
|
100 | full!($i, call!($f));
| ^
...
258 | / named!(one_literal<&[u8],EvalResult,::Error>,
259 | | fix_error!(::Error,alt_complete!(
260 | | map!(full!(c_char),EvalResult::Char) |
261 | | map!(full!(c_int),|i|EvalResult::Int(::std::num::Wrapping(i))) |
... |
264 | | ))
265 | | );
| |_- 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 rust-lang/rust#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 full
= note: #[allow(semicolon_in_expressions_from_macros)] on by default
= note: this warning originates in the macro full which comes from the expansion of the macro named (in Nightly builds, run with -Z macro-backtrace for more info)

[epage]

cexpr v0.3.6 has the following newer versions available: 0.4.0, 0.5.0, 0.6.0

The current version of cexpr is 0.6 which has nom 0.7 which doesn't have the future-incompat. The fix in nom was backported to 0.5 (rust-bakery/nom@6ca8614) but not to 0.4. However, likely the best fix is for others to upgrade their version of cexpr.