You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because warp has dependencies to multipart -> buf_redux, which contains feature incompatibilities.
Clippy warning
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:
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):
The package buf_redux v0.8.4 currently triggers the following future incompatibility lints:
warning: trailing semicolon in macro used in expression position
--> /Users/rekby/.cargo/registry/src/github.com-1ecc6299db9ec823/buf_redux-0.8.4/src/policy.rs:25:57
|
25 | ($val:expr) => ( return $crate::policy::DoRead($val); );
| ^
...
118 | if buffer.len() >= self.0 { do_read!(false) }
| --------------- 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 do_read
= note: #[allow(semicolon_in_expressions_from_macros)] on by default
= note: this warning originates in the macro do_read (in Nightly builds, run with -Z macro-backtrace for more info)
The package multipart v0.18.0 currently triggers the following future incompatibility lints:
warning: trailing semicolon in macro used in expression position
--> /Users/rekby/.cargo/registry/src/github.com-1ecc6299db9ec823/multipart-0.18.0/src/server/field.rs:30:11
|
30 | ));
| ^
...
174 | None => invalid_cont_disp!(
| ________-
175 | | "expected additional data after Content-Disposition type",
176 | | header.val
177 | | ),
| |- 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: #[allow(semicolon_in_expressions_from_macros)] on by default
= note: this warning originates in the macro invalid_cont_disp (in Nightly builds, run with -Z macro-backtrace for more info)
warning: trailing semicolon in macro used in expression position
--> /Users/rekby/.cargo/registry/src/github.com-1ecc6299db9ec823/multipart-0.18.0/src/server/field.rs:30:11
|
30 | ));
| ^
...
182 | None => invalid_cont_disp!(
| ________-
183 | | "expected field name and maybe filename, got",
184 | | after_disp_type
185 | | ),
| |- 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: #[allow(semicolon_in_expressions_from_macros)] on by default
= note: this warning originates in the macro invalid_cont_disp (in Nightly builds, run with -Z macro-backtrace for more info)
The text was updated successfully, but these errors were encountered:
After merged end released seanmonstar/warp#846
Because warp has dependencies to multipart -> buf_redux, which contains feature incompatibilities.
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:
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):
[email protected]
Repository: https://github.com/abonander/buf_redux
Detailed warning command:
cargo report future-incompatibilities --id 5 --package [email protected]
[email protected]
Repository: http://github.com/abonander/multipart
Detailed warning command:
cargo report future-incompatibilities --id 5 --package [email protected]
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 moreinformation, see:
https://doc.rust-lang.org/cargo/reference/overriding-dependencies.html#the-patch-section
The package
buf_redux v0.8.4
currently triggers the following future incompatibility lints:The package
multipart v0.18.0
currently triggers the following future incompatibility lints:The text was updated successfully, but these errors were encountered: