[INFO] cloning repository https://github.com/KevinMGranger/nine
[INFO] running `Command { std: "git" "-c" "credential.helper=" "-c" "credential.helper=/workspace/cargo-home/bin/git-credential-null" "clone" "--bare" "https://github.com/KevinMGranger/nine" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2FKevinMGranger%2Fnine", kill_on_drop: false }`
[INFO] [stderr] Cloning into bare repository '/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2FKevinMGranger%2Fnine'...
[INFO] running `Command { std: "git" "rev-parse" "HEAD", kill_on_drop: false }`
[INFO] [stdout] e7845cc077b3df77d43bbce258b830ca74d57153
[INFO] checking KevinMGranger/nine against 760e1de835e253bf28bbcbfee38b5e8ed9ffe074 for pr-133502-26
[INFO] running `Command { std: "git" "clone" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2FKevinMGranger%2Fnine" "/workspace/builds/worker-6-tc2/source", kill_on_drop: false }`
[INFO] [stderr] Cloning into '/workspace/builds/worker-6-tc2/source'...
[INFO] [stderr] done.
[INFO] started tweaking git repo https://github.com/KevinMGranger/nine
[INFO] finished tweaking git repo https://github.com/KevinMGranger/nine
[INFO] tweaked toml for git repo https://github.com/KevinMGranger/nine written to /workspace/builds/worker-6-tc2/source/Cargo.toml
[INFO] validating manifest of git repo https://github.com/KevinMGranger/nine on toolchain 760e1de835e253bf28bbcbfee38b5e8ed9ffe074
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+760e1de835e253bf28bbcbfee38b5e8ed9ffe074" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] crate git repo https://github.com/KevinMGranger/nine already has a lockfile, it will not be regenerated
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+760e1de835e253bf28bbcbfee38b5e8ed9ffe074" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Blocking waiting for file lock on package cache
[INFO] [stderr]     Blocking waiting for file lock on package cache
[INFO] [stderr]  Downloading crates ...
[INFO] [stderr]   Downloaded proc-macro2 v1.0.26
[INFO] [stderr]   Downloaded once_cell v1.7.2
[INFO] [stderr]   Downloaded enum_dispatch v0.3.6
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-m" "1610612736" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:1fa6594d87c8fa7b311925a7a77a16f539833322d9dfba4ce891f211db2f90b1" "sleep" "infinity", kill_on_drop: false }`
[INFO] [stdout] 85187173da92fdbe8c034f9879ee2a3270a050342756767f6909304343cbfd31
[INFO] running `Command { std: "docker" "start" "85187173da92fdbe8c034f9879ee2a3270a050342756767f6909304343cbfd31", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "85187173da92fdbe8c034f9879ee2a3270a050342756767f6909304343cbfd31", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "exec" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-w" "/opt/rustwide/workdir" "--user" "0:0" "85187173da92fdbe8c034f9879ee2a3270a050342756767f6909304343cbfd31" "/opt/rustwide/cargo-home/bin/cargo" "+760e1de835e253bf28bbcbfee38b5e8ed9ffe074" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "85187173da92fdbe8c034f9879ee2a3270a050342756767f6909304343cbfd31", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "exec" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-w" "/opt/rustwide/workdir" "--user" "0:0" "85187173da92fdbe8c034f9879ee2a3270a050342756767f6909304343cbfd31" "/opt/rustwide/cargo-home/bin/cargo" "+760e1de835e253bf28bbcbfee38b5e8ed9ffe074" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }`
[INFO] [stderr]    Compiling proc-macro2 v1.0.26
[INFO] [stderr]    Compiling unicode-xid v0.2.0
[INFO] [stderr]    Compiling syn v1.0.72
[INFO] [stderr]    Compiling serde v1.0.102
[INFO] [stderr]    Compiling byteorder v1.3.2
[INFO] [stderr]    Compiling once_cell v1.7.2
[INFO] [stderr]     Checking bytes v1.0.1
[INFO] [stderr]    Compiling quote v1.0.2
[INFO] [stderr]    Compiling thiserror-impl v1.0.24
[INFO] [stderr]    Compiling serde_derive v1.0.102
[INFO] [stderr]    Compiling enum_dispatch v0.3.6
[INFO] [stderr]     Checking thiserror v1.0.24
[INFO] [stderr]     Checking nine v0.6.2 (/opt/rustwide/workdir)
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]  --> src/p2000/l.rs:8:10
[INFO] [stdout]   |
[INFO] [stdout] 8 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]   |          ^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]   = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]  --> src/p2000/l.rs:8:21
[INFO] [stdout]   |
[INFO] [stdout] 8 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]   |                     ^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]   = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000/l.rs:17:10
[INFO] [stdout]    |
[INFO] [stdout] 17 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |          ^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000/l.rs:17:21
[INFO] [stdout]    |
[INFO] [stdout] 17 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |                     ^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000/l.rs:27:10
[INFO] [stdout]    |
[INFO] [stdout] 27 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |          ^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000/l.rs:27:21
[INFO] [stdout]    |
[INFO] [stdout] 27 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |                     ^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000/l.rs:33:10
[INFO] [stdout]    |
[INFO] [stdout] 33 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |          ^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000/l.rs:33:21
[INFO] [stdout]    |
[INFO] [stdout] 33 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |                     ^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000/l.rs:39:10
[INFO] [stdout]    |
[INFO] [stdout] 39 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |          ^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000/l.rs:39:21
[INFO] [stdout]    |
[INFO] [stdout] 39 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |                     ^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000/l.rs:53:10
[INFO] [stdout]    |
[INFO] [stdout] 53 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |          ^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000/l.rs:53:21
[INFO] [stdout]    |
[INFO] [stdout] 53 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |                     ^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000/l.rs:60:10
[INFO] [stdout]    |
[INFO] [stdout] 60 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |          ^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000/l.rs:60:21
[INFO] [stdout]    |
[INFO] [stdout] 60 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |                     ^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000/l.rs:67:10
[INFO] [stdout]    |
[INFO] [stdout] 67 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |          ^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000/l.rs:67:21
[INFO] [stdout]    |
[INFO] [stdout] 67 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |                     ^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000/l.rs:77:10
[INFO] [stdout]    |
[INFO] [stdout] 77 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |          ^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000/l.rs:77:21
[INFO] [stdout]    |
[INFO] [stdout] 77 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |                     ^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000/l.rs:84:10
[INFO] [stdout]    |
[INFO] [stdout] 84 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |          ^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000/l.rs:84:21
[INFO] [stdout]    |
[INFO] [stdout] 84 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |                     ^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000/l.rs:93:10
[INFO] [stdout]    |
[INFO] [stdout] 93 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |          ^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000/l.rs:93:21
[INFO] [stdout]    |
[INFO] [stdout] 93 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |                     ^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000/l.rs:99:10
[INFO] [stdout]    |
[INFO] [stdout] 99 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |          ^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000/l.rs:99:21
[INFO] [stdout]    |
[INFO] [stdout] 99 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |                     ^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/p2000/l.rs:110:10
[INFO] [stdout]     |
[INFO] [stdout] 110 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |          ^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/p2000/l.rs:110:21
[INFO] [stdout]     |
[INFO] [stdout] 110 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |                     ^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/p2000/l.rs:116:10
[INFO] [stdout]     |
[INFO] [stdout] 116 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |          ^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]  --> src/p2000/l.rs:8:10
[INFO] [stdout]   |
[INFO] [stdout] 8 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]   |          ^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]   = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]  --> src/p2000/l.rs:8:21
[INFO] [stdout]   |
[INFO] [stdout] 8 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]   |                     ^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]   = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000/l.rs:17:10
[INFO] [stdout]    |
[INFO] [stdout] 17 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |          ^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000/l.rs:17:21
[INFO] [stdout]    |
[INFO] [stdout] 17 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |                     ^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000/l.rs:27:10
[INFO] [stdout]    |
[INFO] [stdout] 27 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |          ^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000/l.rs:27:21
[INFO] [stdout]    |
[INFO] [stdout] 27 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |                     ^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000/l.rs:33:10
[INFO] [stdout]    |
[INFO] [stdout] 33 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |          ^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000/l.rs:33:21
[INFO] [stdout]    |
[INFO] [stdout] 33 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |                     ^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000/l.rs:39:10
[INFO] [stdout]    |
[INFO] [stdout] 39 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |          ^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000/l.rs:39:21
[INFO] [stdout]    |
[INFO] [stdout] 39 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |                     ^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000/l.rs:53:10
[INFO] [stdout]    |
[INFO] [stdout] 53 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |          ^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000/l.rs:53:21
[INFO] [stdout]    |
[INFO] [stdout] 53 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |                     ^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000/l.rs:60:10
[INFO] [stdout]    |
[INFO] [stdout] 60 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |          ^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000/l.rs:60:21
[INFO] [stdout]    |
[INFO] [stdout] 60 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |                     ^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000/l.rs:67:10
[INFO] [stdout]    |
[INFO] [stdout] 67 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |          ^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/p2000/l.rs:116:21
[INFO] [stdout]     |
[INFO] [stdout] 116 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |                     ^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/p2000/l.rs:124:10
[INFO] [stdout]     |
[INFO] [stdout] 124 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |          ^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/p2000/l.rs:124:21
[INFO] [stdout]     |
[INFO] [stdout] 124 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |                     ^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/p2000/l.rs:129:10
[INFO] [stdout]     |
[INFO] [stdout] 129 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |          ^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/p2000/l.rs:129:21
[INFO] [stdout]     |
[INFO] [stdout] 129 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |                     ^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/p2000/l.rs:135:10
[INFO] [stdout]     |
[INFO] [stdout] 135 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |          ^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/p2000/l.rs:135:21
[INFO] [stdout]     |
[INFO] [stdout] 135 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |                     ^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/p2000/l.rs:141:10
[INFO] [stdout]     |
[INFO] [stdout] 141 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |          ^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/p2000/l.rs:141:21
[INFO] [stdout]     |
[INFO] [stdout] 141 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |                     ^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/p2000/l.rs:149:10
[INFO] [stdout]     |
[INFO] [stdout] 149 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |          ^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/p2000/l.rs:149:21
[INFO] [stdout]     |
[INFO] [stdout] 149 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |                     ^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/p2000/l.rs:179:10
[INFO] [stdout]     |
[INFO] [stdout] 179 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |          ^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/p2000/l.rs:179:21
[INFO] [stdout]     |
[INFO] [stdout] 179 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |                     ^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/p2000/l.rs:194:10
[INFO] [stdout]     |
[INFO] [stdout] 194 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |          ^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/p2000/l.rs:194:21
[INFO] [stdout]     |
[INFO] [stdout] 194 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |                     ^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]  --> src/p2000/u.rs:8:10
[INFO] [stdout]   |
[INFO] [stdout] 8 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]   |          ^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]   = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]  --> src/p2000/u.rs:8:21
[INFO] [stdout]   |
[INFO] [stdout] 8 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]   |                     ^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]   = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000/u.rs:15:10
[INFO] [stdout]    |
[INFO] [stdout] 15 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |          ^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000/u.rs:15:21
[INFO] [stdout]    |
[INFO] [stdout] 15 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |                     ^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000.rs:17:14
[INFO] [stdout]    |
[INFO] [stdout] 17 |     #[derive(Serialize, Deserialize)]
[INFO] [stdout]    |              ^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000.rs:17:25
[INFO] [stdout]    |
[INFO] [stdout] 17 |     #[derive(Serialize, Deserialize)]
[INFO] [stdout]    |                         ^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000.rs:31:14
[INFO] [stdout]    |
[INFO] [stdout] 31 |     #[derive(Serialize, Deserialize)]
[INFO] [stdout]    |              ^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000.rs:31:25
[INFO] [stdout]    |
[INFO] [stdout] 31 |     #[derive(Serialize, Deserialize)]
[INFO] [stdout]    |                         ^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000.rs:60:14
[INFO] [stdout]    |
[INFO] [stdout] 60 |     #[derive(Serialize, Deserialize)]
[INFO] [stdout]    |              ^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000.rs:60:25
[INFO] [stdout]    |
[INFO] [stdout] 60 |     #[derive(Serialize, Deserialize)]
[INFO] [stdout]    |                         ^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000.rs:94:10
[INFO] [stdout]    |
[INFO] [stdout] 94 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq, Clone)]
[INFO] [stdout]    |          ^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000.rs:94:21
[INFO] [stdout]    |
[INFO] [stdout] 94 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq, Clone)]
[INFO] [stdout]    |                     ^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/p2000.rs:101:10
[INFO] [stdout]     |
[INFO] [stdout] 101 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq, Clone)]
[INFO] [stdout]     |          ^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000/l.rs:67:21
[INFO] [stdout]    |
[INFO] [stdout] 67 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |                     ^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000/l.rs:77:10
[INFO] [stdout]    |
[INFO] [stdout] 77 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |          ^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000/l.rs:77:21
[INFO] [stdout]    |
[INFO] [stdout] 77 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |                     ^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000/l.rs:84:10
[INFO] [stdout]    |
[INFO] [stdout] 84 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |          ^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000/l.rs:84:21
[INFO] [stdout]    |
[INFO] [stdout] 84 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |                     ^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000/l.rs:93:10
[INFO] [stdout]    |
[INFO] [stdout] 93 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |          ^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000/l.rs:93:21
[INFO] [stdout]    |
[INFO] [stdout] 93 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |                     ^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000/l.rs:99:10
[INFO] [stdout]    |
[INFO] [stdout] 99 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |          ^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000/l.rs:99:21
[INFO] [stdout]    |
[INFO] [stdout] 99 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |                     ^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/p2000/l.rs:110:10
[INFO] [stdout]     |
[INFO] [stdout] 110 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |          ^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/p2000/l.rs:110:21
[INFO] [stdout]     |
[INFO] [stdout] 110 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |                     ^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/p2000/l.rs:116:10
[INFO] [stdout]     |
[INFO] [stdout] 116 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |          ^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/p2000/l.rs:116:21
[INFO] [stdout]     |
[INFO] [stdout] 116 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |                     ^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/p2000/l.rs:124:10
[INFO] [stdout]     |
[INFO] [stdout] 124 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |          ^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/p2000/l.rs:124:21
[INFO] [stdout]     |
[INFO] [stdout] 124 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |                     ^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/p2000/l.rs:129:10
[INFO] [stdout]     |
[INFO] [stdout] 129 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |          ^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/p2000.rs:101:21
[INFO] [stdout]     |
[INFO] [stdout] 101 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq, Clone)]
[INFO] [stdout]     |                     ^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/p2000/l.rs:129:21
[INFO] [stdout]     |
[INFO] [stdout] 129 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |                     ^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/p2000/l.rs:135:10
[INFO] [stdout]     |
[INFO] [stdout] 135 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |          ^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/p2000/l.rs:135:21
[INFO] [stdout]     |
[INFO] [stdout] 135 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |                     ^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/p2000/l.rs:141:10
[INFO] [stdout]     |
[INFO] [stdout] 141 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |          ^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/p2000/l.rs:141:21
[INFO] [stdout]     |
[INFO] [stdout] 141 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |                     ^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/p2000/l.rs:149:10
[INFO] [stdout]     |
[INFO] [stdout] 149 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |          ^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/p2000/l.rs:149:21
[INFO] [stdout]     |
[INFO] [stdout] 149 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |                     ^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/p2000/l.rs:179:10
[INFO] [stdout]     |
[INFO] [stdout] 179 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |          ^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/p2000/l.rs:179:21
[INFO] [stdout]     |
[INFO] [stdout] 179 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |                     ^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/p2000/l.rs:194:10
[INFO] [stdout]     |
[INFO] [stdout] 194 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |          ^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/p2000/l.rs:194:21
[INFO] [stdout]     |
[INFO] [stdout] 194 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |                     ^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]  --> src/p2000/u.rs:8:10
[INFO] [stdout]   |
[INFO] [stdout] 8 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]   |          ^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]   = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]  --> src/p2000/u.rs:8:21
[INFO] [stdout]   |
[INFO] [stdout] 8 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]   |                     ^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]   = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000/u.rs:15:10
[INFO] [stdout]    |
[INFO] [stdout] 15 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |          ^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000/u.rs:15:21
[INFO] [stdout]    |
[INFO] [stdout] 15 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |                     ^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000.rs:17:14
[INFO] [stdout]    |
[INFO] [stdout] 17 |     #[derive(Serialize, Deserialize)]
[INFO] [stdout]    |              ^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000.rs:17:25
[INFO] [stdout]    |
[INFO] [stdout] 17 |     #[derive(Serialize, Deserialize)]
[INFO] [stdout]    |                         ^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000.rs:31:14
[INFO] [stdout]    |
[INFO] [stdout] 31 |     #[derive(Serialize, Deserialize)]
[INFO] [stdout]    |              ^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000.rs:31:25
[INFO] [stdout]    |
[INFO] [stdout] 31 |     #[derive(Serialize, Deserialize)]
[INFO] [stdout]    |                         ^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000.rs:60:14
[INFO] [stdout]    |
[INFO] [stdout] 60 |     #[derive(Serialize, Deserialize)]
[INFO] [stdout]    |              ^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000.rs:60:25
[INFO] [stdout]    |
[INFO] [stdout] 60 |     #[derive(Serialize, Deserialize)]
[INFO] [stdout]    |                         ^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000.rs:94:10
[INFO] [stdout]    |
[INFO] [stdout] 94 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq, Clone)]
[INFO] [stdout]    |          ^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/p2000.rs:94:21
[INFO] [stdout]    |
[INFO] [stdout] 94 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq, Clone)]
[INFO] [stdout]    |                     ^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/p2000.rs:101:10
[INFO] [stdout]     |
[INFO] [stdout] 101 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq, Clone)]
[INFO] [stdout]     |          ^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/p2000.rs:101:21
[INFO] [stdout]     |
[INFO] [stdout] 101 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq, Clone)]
[INFO] [stdout]     |                     ^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: ambiguous glob re-exports
[INFO] [stdout]   --> src/ser.rs:9:9
[INFO] [stdout]    |
[INFO] [stdout]  9 | pub use write_seek::*;
[INFO] [stdout]    |         ^^^^^^^^^^^^^ the name `CountingSequenceSerializer` in the type namespace is first re-exported here
[INFO] [stdout] ...
[INFO] [stdout] 12 | pub use count::*;
[INFO] [stdout]    |         -------- but the name `CountingSequenceSerializer` in the type namespace is also re-exported here
[INFO] [stdout]    |
[INFO] [stdout]    = note: `#[warn(ambiguous_glob_reexports)]` on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: ambiguous glob re-exports
[INFO] [stdout]   --> src/ser.rs:9:9
[INFO] [stdout]    |
[INFO] [stdout]  9 | pub use write_seek::*;
[INFO] [stdout]    |         ^^^^^^^^^^^^^ the name `AccountingStructSerializer` in the type namespace is first re-exported here
[INFO] [stdout] ...
[INFO] [stdout] 12 | pub use count::*;
[INFO] [stdout]    |         -------- but the name `AccountingStructSerializer` in the type namespace is also re-exported here
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:22
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]    --> src/message.rs:68:42
[INFO] [stdout]     |
[INFO] [stdout]  68 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `serde::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: ambiguous glob re-exports
[INFO] [stdout]   --> src/ser.rs:9:9
[INFO] [stdout]    |
[INFO] [stdout]  9 | pub use write_seek::*;
[INFO] [stdout]    |         ^^^^^^^^^^^^^ the name `CountingSequenceSerializer` in the type namespace is first re-exported here
[INFO] [stdout] ...
[INFO] [stdout] 12 | pub use count::*;
[INFO] [stdout]    |         -------- but the name `CountingSequenceSerializer` in the type namespace is also re-exported here
[INFO] [stdout]    |
[INFO] [stdout]    = note: `#[warn(ambiguous_glob_reexports)]` on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: ambiguous glob re-exports
[INFO] [stdout]   --> src/ser.rs:9:9
[INFO] [stdout]    |
[INFO] [stdout]  9 | pub use write_seek::*;
[INFO] [stdout]    |         ^^^^^^^^^^^^^ the name `AccountingStructSerializer` in the type namespace is first re-exported here
[INFO] [stdout] ...
[INFO] [stdout] 12 | pub use count::*;
[INFO] [stdout]    |         -------- but the name `AccountingStructSerializer` in the type namespace is also re-exported here
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000.rs:17:14
[INFO] [stdout]    |
[INFO] [stdout] 17 |     #[derive(Serialize, Deserialize)]
[INFO] [stdout]    |              ^--------
[INFO] [stdout]    |              |
[INFO] [stdout]    |              `Serialize` is not local
[INFO] [stdout]    |              move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_FileType`
[INFO] [stdout] 18 |     pub struct FileType: u8 {
[INFO] [stdout]    |                -------- `FileType` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: `#[warn(non_local_definitions)]` on by default
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000.rs:17:25
[INFO] [stdout]    |
[INFO] [stdout] 17 |     #[derive(Serialize, Deserialize)]
[INFO] [stdout]    |                         ^----------
[INFO] [stdout]    |                         |
[INFO] [stdout]    |                         `Deserialize` is not local
[INFO] [stdout]    |                         move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_FileType`
[INFO] [stdout] 18 |     pub struct FileType: u8 {
[INFO] [stdout]    |                -------- `FileType` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000.rs:31:14
[INFO] [stdout]    |
[INFO] [stdout] 31 |     #[derive(Serialize, Deserialize)]
[INFO] [stdout]    |              ^--------
[INFO] [stdout]    |              |
[INFO] [stdout]    |              `Serialize` is not local
[INFO] [stdout]    |              move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_OpenMode`
[INFO] [stdout] 32 |     pub struct OpenMode: u8 {
[INFO] [stdout]    |                -------- `OpenMode` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000.rs:31:25
[INFO] [stdout]    |
[INFO] [stdout] 31 |     #[derive(Serialize, Deserialize)]
[INFO] [stdout]    |                         ^----------
[INFO] [stdout]    |                         |
[INFO] [stdout]    |                         `Deserialize` is not local
[INFO] [stdout]    |                         move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_OpenMode`
[INFO] [stdout] 32 |     pub struct OpenMode: u8 {
[INFO] [stdout]    |                -------- `OpenMode` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000.rs:60:14
[INFO] [stdout]    |
[INFO] [stdout] 60 |     #[derive(Serialize, Deserialize)]
[INFO] [stdout]    |              ^--------
[INFO] [stdout]    |              |
[INFO] [stdout]    |              `Serialize` is not local
[INFO] [stdout]    |              move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_FileMode`
[INFO] [stdout] 61 |     pub struct FileMode: u32 {
[INFO] [stdout]    |                -------- `FileMode` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000.rs:60:25
[INFO] [stdout]    |
[INFO] [stdout] 60 |     #[derive(Serialize, Deserialize)]
[INFO] [stdout]    |                         ^----------
[INFO] [stdout]    |                         |
[INFO] [stdout]    |                         `Deserialize` is not local
[INFO] [stdout]    |                         move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_FileMode`
[INFO] [stdout] 61 |     pub struct FileMode: u32 {
[INFO] [stdout]    |                -------- `FileMode` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000.rs:94:10
[INFO] [stdout]    |
[INFO] [stdout] 94 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq, Clone)]
[INFO] [stdout]    |          ^--------
[INFO] [stdout]    |          |
[INFO] [stdout]    |          `Serialize` is not local
[INFO] [stdout]    |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Qid`
[INFO] [stdout] 95 | pub struct Qid {
[INFO] [stdout]    |            --- `Qid` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000.rs:94:21
[INFO] [stdout]    |
[INFO] [stdout] 94 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq, Clone)]
[INFO] [stdout]    |                     ^----------
[INFO] [stdout]    |                     |
[INFO] [stdout]    |                     `Deserialize` is not local
[INFO] [stdout]    |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Qid`
[INFO] [stdout] 95 | pub struct Qid {
[INFO] [stdout]    |            --- `Qid` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/p2000.rs:101:10
[INFO] [stdout]     |
[INFO] [stdout] 101 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq, Clone)]
[INFO] [stdout]     |          ^--------
[INFO] [stdout]     |          |
[INFO] [stdout]     |          `Serialize` is not local
[INFO] [stdout]     |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Stat`
[INFO] [stdout] 102 | pub struct Stat {
[INFO] [stdout]     |            ---- `Stat` is not local
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/p2000.rs:101:21
[INFO] [stdout]     |
[INFO] [stdout] 101 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq, Clone)]
[INFO] [stdout]     |                     ^----------
[INFO] [stdout]     |                     |
[INFO] [stdout]     |                     `Deserialize` is not local
[INFO] [stdout]     |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Stat`
[INFO] [stdout] 102 | pub struct Stat {
[INFO] [stdout]     |            ---- `Stat` is not local
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]  --> src/p2000/l.rs:8:10
[INFO] [stdout]   |
[INFO] [stdout] 8 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]   |          ^--------
[INFO] [stdout]   |          |
[INFO] [stdout]   |          `Serialize` is not local
[INFO] [stdout]   |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Tauth`
[INFO] [stdout] 9 | pub struct Tauth {
[INFO] [stdout]   |            ----- `Tauth` is not local
[INFO] [stdout]   |
[INFO] [stdout]   = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]   = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]   = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]   = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]   = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]  --> src/p2000/l.rs:8:21
[INFO] [stdout]   |
[INFO] [stdout] 8 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]   |                     ^----------
[INFO] [stdout]   |                     |
[INFO] [stdout]   |                     `Deserialize` is not local
[INFO] [stdout]   |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Tauth`
[INFO] [stdout] 9 | pub struct Tauth {
[INFO] [stdout]   |            ----- `Tauth` is not local
[INFO] [stdout]   |
[INFO] [stdout]   = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]   = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]   = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]   = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]   = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000/l.rs:17:10
[INFO] [stdout]    |
[INFO] [stdout] 17 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |          ^--------
[INFO] [stdout]    |          |
[INFO] [stdout]    |          `Serialize` is not local
[INFO] [stdout]    |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Tattach`
[INFO] [stdout] 18 | pub struct Tattach {
[INFO] [stdout]    |            ------- `Tattach` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000/l.rs:17:21
[INFO] [stdout]    |
[INFO] [stdout] 17 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |                     ^----------
[INFO] [stdout]    |                     |
[INFO] [stdout]    |                     `Deserialize` is not local
[INFO] [stdout]    |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Tattach`
[INFO] [stdout] 18 | pub struct Tattach {
[INFO] [stdout]    |            ------- `Tattach` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000/l.rs:27:10
[INFO] [stdout]    |
[INFO] [stdout] 27 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |          ^--------
[INFO] [stdout]    |          |
[INFO] [stdout]    |          `Serialize` is not local
[INFO] [stdout]    |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Rlerror`
[INFO] [stdout] 28 | pub struct Rlerror {
[INFO] [stdout]    |            ------- `Rlerror` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000/l.rs:27:21
[INFO] [stdout]    |
[INFO] [stdout] 27 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |                     ^----------
[INFO] [stdout]    |                     |
[INFO] [stdout]    |                     `Deserialize` is not local
[INFO] [stdout]    |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Rlerror`
[INFO] [stdout] 28 | pub struct Rlerror {
[INFO] [stdout]    |            ------- `Rlerror` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000/l.rs:33:10
[INFO] [stdout]    |
[INFO] [stdout] 33 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |          ^--------
[INFO] [stdout]    |          |
[INFO] [stdout]    |          `Serialize` is not local
[INFO] [stdout]    |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Tstatfs`
[INFO] [stdout] 34 | pub struct Tstatfs {
[INFO] [stdout]    |            ------- `Tstatfs` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000/l.rs:33:21
[INFO] [stdout]    |
[INFO] [stdout] 33 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |                     ^----------
[INFO] [stdout]    |                     |
[INFO] [stdout]    |                     `Deserialize` is not local
[INFO] [stdout]    |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Tstatfs`
[INFO] [stdout] 34 | pub struct Tstatfs {
[INFO] [stdout]    |            ------- `Tstatfs` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000/l.rs:39:10
[INFO] [stdout]    |
[INFO] [stdout] 39 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |          ^--------
[INFO] [stdout]    |          |
[INFO] [stdout]    |          `Serialize` is not local
[INFO] [stdout]    |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Rstatfs`
[INFO] [stdout] 40 | pub struct Rstatfs {
[INFO] [stdout]    |            ------- `Rstatfs` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000/l.rs:39:21
[INFO] [stdout]    |
[INFO] [stdout] 39 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |                     ^----------
[INFO] [stdout]    |                     |
[INFO] [stdout]    |                     `Deserialize` is not local
[INFO] [stdout]    |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Rstatfs`
[INFO] [stdout] 40 | pub struct Rstatfs {
[INFO] [stdout]    |            ------- `Rstatfs` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000/l.rs:53:10
[INFO] [stdout]    |
[INFO] [stdout] 53 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |          ^--------
[INFO] [stdout]    |          |
[INFO] [stdout]    |          `Serialize` is not local
[INFO] [stdout]    |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Tlopen`
[INFO] [stdout] 54 | pub struct Tlopen {
[INFO] [stdout]    |            ------ `Tlopen` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000/l.rs:53:21
[INFO] [stdout]    |
[INFO] [stdout] 53 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |                     ^----------
[INFO] [stdout]    |                     |
[INFO] [stdout]    |                     `Deserialize` is not local
[INFO] [stdout]    |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Tlopen`
[INFO] [stdout] 54 | pub struct Tlopen {
[INFO] [stdout]    |            ------ `Tlopen` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000/l.rs:60:10
[INFO] [stdout]    |
[INFO] [stdout] 60 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |          ^--------
[INFO] [stdout]    |          |
[INFO] [stdout]    |          `Serialize` is not local
[INFO] [stdout]    |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Rlopen`
[INFO] [stdout] 61 | pub struct Rlopen {
[INFO] [stdout]    |            ------ `Rlopen` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000/l.rs:60:21
[INFO] [stdout]    |
[INFO] [stdout] 60 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |                     ^----------
[INFO] [stdout]    |                     |
[INFO] [stdout]    |                     `Deserialize` is not local
[INFO] [stdout]    |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Rlopen`
[INFO] [stdout] 61 | pub struct Rlopen {
[INFO] [stdout]    |            ------ `Rlopen` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000/l.rs:67:10
[INFO] [stdout]    |
[INFO] [stdout] 67 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |          ^--------
[INFO] [stdout]    |          |
[INFO] [stdout]    |          `Serialize` is not local
[INFO] [stdout]    |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Tlcreate`
[INFO] [stdout] 68 | pub struct Tlcreate {
[INFO] [stdout]    |            -------- `Tlcreate` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000/l.rs:67:21
[INFO] [stdout]    |
[INFO] [stdout] 67 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |                     ^----------
[INFO] [stdout]    |                     |
[INFO] [stdout]    |                     `Deserialize` is not local
[INFO] [stdout]    |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Tlcreate`
[INFO] [stdout] 68 | pub struct Tlcreate {
[INFO] [stdout]    |            -------- `Tlcreate` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000/l.rs:77:10
[INFO] [stdout]    |
[INFO] [stdout] 77 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |          ^--------
[INFO] [stdout]    |          |
[INFO] [stdout]    |          `Serialize` is not local
[INFO] [stdout]    |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Rlcreate`
[INFO] [stdout] 78 | pub struct Rlcreate {
[INFO] [stdout]    |            -------- `Rlcreate` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000/l.rs:77:21
[INFO] [stdout]    |
[INFO] [stdout] 77 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |                     ^----------
[INFO] [stdout]    |                     |
[INFO] [stdout]    |                     `Deserialize` is not local
[INFO] [stdout]    |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Rlcreate`
[INFO] [stdout] 78 | pub struct Rlcreate {
[INFO] [stdout]    |            -------- `Rlcreate` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000/l.rs:84:10
[INFO] [stdout]    |
[INFO] [stdout] 84 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |          ^--------
[INFO] [stdout]    |          |
[INFO] [stdout]    |          `Serialize` is not local
[INFO] [stdout]    |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Tsymlink`
[INFO] [stdout] 85 | pub struct Tsymlink {
[INFO] [stdout]    |            -------- `Tsymlink` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000/l.rs:84:21
[INFO] [stdout]    |
[INFO] [stdout] 84 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |                     ^----------
[INFO] [stdout]    |                     |
[INFO] [stdout]    |                     `Deserialize` is not local
[INFO] [stdout]    |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Tsymlink`
[INFO] [stdout] 85 | pub struct Tsymlink {
[INFO] [stdout]    |            -------- `Tsymlink` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000/l.rs:93:10
[INFO] [stdout]    |
[INFO] [stdout] 93 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |          ^--------
[INFO] [stdout]    |          |
[INFO] [stdout]    |          `Serialize` is not local
[INFO] [stdout]    |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Rsymlink`
[INFO] [stdout] 94 | pub struct Rsymlink {
[INFO] [stdout]    |            -------- `Rsymlink` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000/l.rs:93:21
[INFO] [stdout]    |
[INFO] [stdout] 93 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |                     ^----------
[INFO] [stdout]    |                     |
[INFO] [stdout]    |                     `Deserialize` is not local
[INFO] [stdout]    |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Rsymlink`
[INFO] [stdout] 94 | pub struct Rsymlink {
[INFO] [stdout]    |            -------- `Rsymlink` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/p2000/l.rs:99:10
[INFO] [stdout]     |
[INFO] [stdout]  99 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |          ^--------
[INFO] [stdout]     |          |
[INFO] [stdout]     |          `Serialize` is not local
[INFO] [stdout]     |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Tmknod`
[INFO] [stdout] 100 | pub struct Tmknod {
[INFO] [stdout]     |            ------ `Tmknod` is not local
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/p2000/l.rs:99:21
[INFO] [stdout]     |
[INFO] [stdout]  99 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |                     ^----------
[INFO] [stdout]     |                     |
[INFO] [stdout]     |                     `Deserialize` is not local
[INFO] [stdout]     |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Tmknod`
[INFO] [stdout] 100 | pub struct Tmknod {
[INFO] [stdout]     |            ------ `Tmknod` is not local
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/p2000/l.rs:110:10
[INFO] [stdout]     |
[INFO] [stdout] 110 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |          ^--------
[INFO] [stdout]     |          |
[INFO] [stdout]     |          `Serialize` is not local
[INFO] [stdout]     |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Rmknod`
[INFO] [stdout] 111 | pub struct Rmknod {
[INFO] [stdout]     |            ------ `Rmknod` is not local
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/p2000/l.rs:110:21
[INFO] [stdout]     |
[INFO] [stdout] 110 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |                     ^----------
[INFO] [stdout]     |                     |
[INFO] [stdout]     |                     `Deserialize` is not local
[INFO] [stdout]     |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Rmknod`
[INFO] [stdout] 111 | pub struct Rmknod {
[INFO] [stdout]     |            ------ `Rmknod` is not local
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/p2000/l.rs:116:10
[INFO] [stdout]     |
[INFO] [stdout] 116 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |          ^--------
[INFO] [stdout]     |          |
[INFO] [stdout]     |          `Serialize` is not local
[INFO] [stdout]     |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Trename`
[INFO] [stdout] 117 | pub struct Trename {
[INFO] [stdout]     |            ------- `Trename` is not local
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/p2000/l.rs:116:21
[INFO] [stdout]     |
[INFO] [stdout] 116 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |                     ^----------
[INFO] [stdout]     |                     |
[INFO] [stdout]     |                     `Deserialize` is not local
[INFO] [stdout]     |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Trename`
[INFO] [stdout] 117 | pub struct Trename {
[INFO] [stdout]     |            ------- `Trename` is not local
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/p2000/l.rs:124:10
[INFO] [stdout]     |
[INFO] [stdout] 124 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |          ^--------
[INFO] [stdout]     |          |
[INFO] [stdout]     |          `Serialize` is not local
[INFO] [stdout]     |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Rrename`
[INFO] [stdout] 125 | pub struct Rrename {
[INFO] [stdout]     |            ------- `Rrename` is not local
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/p2000/l.rs:124:21
[INFO] [stdout]     |
[INFO] [stdout] 124 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |                     ^----------
[INFO] [stdout]     |                     |
[INFO] [stdout]     |                     `Deserialize` is not local
[INFO] [stdout]     |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Rrename`
[INFO] [stdout] 125 | pub struct Rrename {
[INFO] [stdout]     |            ------- `Rrename` is not local
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/p2000/l.rs:129:10
[INFO] [stdout]     |
[INFO] [stdout] 129 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |          ^--------
[INFO] [stdout]     |          |
[INFO] [stdout]     |          `Serialize` is not local
[INFO] [stdout]     |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Treadlink`
[INFO] [stdout] 130 | pub struct Treadlink {
[INFO] [stdout]     |            --------- `Treadlink` is not local
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/p2000/l.rs:129:21
[INFO] [stdout]     |
[INFO] [stdout] 129 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |                     ^----------
[INFO] [stdout]     |                     |
[INFO] [stdout]     |                     `Deserialize` is not local
[INFO] [stdout]     |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Treadlink`
[INFO] [stdout] 130 | pub struct Treadlink {
[INFO] [stdout]     |            --------- `Treadlink` is not local
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/p2000/l.rs:135:10
[INFO] [stdout]     |
[INFO] [stdout] 135 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |          ^--------
[INFO] [stdout]     |          |
[INFO] [stdout]     |          `Serialize` is not local
[INFO] [stdout]     |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Rreadlink`
[INFO] [stdout] 136 | pub struct Rreadlink {
[INFO] [stdout]     |            --------- `Rreadlink` is not local
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/p2000/l.rs:135:21
[INFO] [stdout]     |
[INFO] [stdout] 135 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |                     ^----------
[INFO] [stdout]     |                     |
[INFO] [stdout]     |                     `Deserialize` is not local
[INFO] [stdout]     |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Rreadlink`
[INFO] [stdout] 136 | pub struct Rreadlink {
[INFO] [stdout]     |            --------- `Rreadlink` is not local
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/p2000/l.rs:141:10
[INFO] [stdout]     |
[INFO] [stdout] 141 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |          ^--------
[INFO] [stdout]     |          |
[INFO] [stdout]     |          `Serialize` is not local
[INFO] [stdout]     |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Tgetattr`
[INFO] [stdout] 142 | pub struct Tgetattr {
[INFO] [stdout]     |            -------- `Tgetattr` is not local
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/p2000/l.rs:141:21
[INFO] [stdout]     |
[INFO] [stdout] 141 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |                     ^----------
[INFO] [stdout]     |                     |
[INFO] [stdout]     |                     `Deserialize` is not local
[INFO] [stdout]     |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Tgetattr`
[INFO] [stdout] 142 | pub struct Tgetattr {
[INFO] [stdout]     |            -------- `Tgetattr` is not local
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/p2000/l.rs:149:10
[INFO] [stdout]     |
[INFO] [stdout] 149 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |          ^--------
[INFO] [stdout]     |          |
[INFO] [stdout]     |          `Serialize` is not local
[INFO] [stdout]     |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Rgetattr`
[INFO] [stdout] 150 | pub struct Rgetattr {
[INFO] [stdout]     |            -------- `Rgetattr` is not local
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/p2000/l.rs:149:21
[INFO] [stdout]     |
[INFO] [stdout] 149 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |                     ^----------
[INFO] [stdout]     |                     |
[INFO] [stdout]     |                     `Deserialize` is not local
[INFO] [stdout]     |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Rgetattr`
[INFO] [stdout] 150 | pub struct Rgetattr {
[INFO] [stdout]     |            -------- `Rgetattr` is not local
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/p2000/l.rs:179:10
[INFO] [stdout]     |
[INFO] [stdout] 179 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |          ^--------
[INFO] [stdout]     |          |
[INFO] [stdout]     |          `Serialize` is not local
[INFO] [stdout]     |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Tsetattr`
[INFO] [stdout] 180 | pub struct Tsetattr {
[INFO] [stdout]     |            -------- `Tsetattr` is not local
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/p2000/l.rs:179:21
[INFO] [stdout]     |
[INFO] [stdout] 179 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |                     ^----------
[INFO] [stdout]     |                     |
[INFO] [stdout]     |                     `Deserialize` is not local
[INFO] [stdout]     |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Tsetattr`
[INFO] [stdout] 180 | pub struct Tsetattr {
[INFO] [stdout]     |            -------- `Tsetattr` is not local
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/p2000/l.rs:194:10
[INFO] [stdout]     |
[INFO] [stdout] 194 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |          ^--------
[INFO] [stdout]     |          |
[INFO] [stdout]     |          `Serialize` is not local
[INFO] [stdout]     |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Rsetattr`
[INFO] [stdout] 195 | pub struct Rsetattr {
[INFO] [stdout]     |            -------- `Rsetattr` is not local
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/p2000/l.rs:194:21
[INFO] [stdout]     |
[INFO] [stdout] 194 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |                     ^----------
[INFO] [stdout]     |                     |
[INFO] [stdout]     |                     `Deserialize` is not local
[INFO] [stdout]     |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Rsetattr`
[INFO] [stdout] 195 | pub struct Rsetattr {
[INFO] [stdout]     |            -------- `Rsetattr` is not local
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]  --> src/p2000/u.rs:8:10
[INFO] [stdout]   |
[INFO] [stdout] 8 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]   |          ^--------
[INFO] [stdout]   |          |
[INFO] [stdout]   |          `Serialize` is not local
[INFO] [stdout]   |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Topenfd`
[INFO] [stdout] 9 | pub struct Topenfd {
[INFO] [stdout]   |            ------- `Topenfd` is not local
[INFO] [stdout]   |
[INFO] [stdout]   = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]   = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]   = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]   = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]   = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]  --> src/p2000/u.rs:8:21
[INFO] [stdout]   |
[INFO] [stdout] 8 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]   |                     ^----------
[INFO] [stdout]   |                     |
[INFO] [stdout]   |                     `Deserialize` is not local
[INFO] [stdout]   |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Topenfd`
[INFO] [stdout] 9 | pub struct Topenfd {
[INFO] [stdout]   |            ------- `Topenfd` is not local
[INFO] [stdout]   |
[INFO] [stdout]   = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]   = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]   = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]   = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]   = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000/u.rs:15:10
[INFO] [stdout]    |
[INFO] [stdout] 15 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |          ^--------
[INFO] [stdout]    |          |
[INFO] [stdout]    |          `Serialize` is not local
[INFO] [stdout]    |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Ropenfd`
[INFO] [stdout] 16 | pub struct Ropenfd {
[INFO] [stdout]    |            ------- `Ropenfd` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000/u.rs:15:21
[INFO] [stdout]    |
[INFO] [stdout] 15 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |                     ^----------
[INFO] [stdout]    |                     |
[INFO] [stdout]    |                     `Deserialize` is not local
[INFO] [stdout]    |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Ropenfd`
[INFO] [stdout] 16 | pub struct Ropenfd {
[INFO] [stdout]    |            ------- `Ropenfd` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000.rs:17:14
[INFO] [stdout]    |
[INFO] [stdout] 17 |     #[derive(Serialize, Deserialize)]
[INFO] [stdout]    |              ^--------
[INFO] [stdout]    |              |
[INFO] [stdout]    |              `Serialize` is not local
[INFO] [stdout]    |              move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_FileType`
[INFO] [stdout] 18 |     pub struct FileType: u8 {
[INFO] [stdout]    |                -------- `FileType` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: `#[warn(non_local_definitions)]` on by default
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000.rs:17:25
[INFO] [stdout]    |
[INFO] [stdout] 17 |     #[derive(Serialize, Deserialize)]
[INFO] [stdout]    |                         ^----------
[INFO] [stdout]    |                         |
[INFO] [stdout]    |                         `Deserialize` is not local
[INFO] [stdout]    |                         move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_FileType`
[INFO] [stdout] 18 |     pub struct FileType: u8 {
[INFO] [stdout]    |                -------- `FileType` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^-----------------
[INFO] [stdout]     |                        |
[INFO] [stdout]     |                        `Deserialize` is not local
[INFO] [stdout]     |                        move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Tversion`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout]     | |      -------- `Tversion` is not local
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^---------------
[INFO] [stdout]     |                                            |
[INFO] [stdout]     |                                            `Serialize` is not local
[INFO] [stdout]     |                                            move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Tversion`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout]     | |      -------- `Tversion` is not local
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^-----------------
[INFO] [stdout]     |                        |
[INFO] [stdout]     |                        `Deserialize` is not local
[INFO] [stdout]     |                        move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Rversion`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 141 | |      Rversion {
[INFO] [stdout]     | |      -------- `Rversion` is not local
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000.rs:31:14
[INFO] [stdout]    |
[INFO] [stdout] 31 |     #[derive(Serialize, Deserialize)]
[INFO] [stdout]    |              ^--------
[INFO] [stdout]    |              |
[INFO] [stdout]    |              `Serialize` is not local
[INFO] [stdout]    |              move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_OpenMode`
[INFO] [stdout] 32 |     pub struct OpenMode: u8 {
[INFO] [stdout]    |                -------- `OpenMode` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000.rs:31:25
[INFO] [stdout]    |
[INFO] [stdout] 31 |     #[derive(Serialize, Deserialize)]
[INFO] [stdout]    |                         ^----------
[INFO] [stdout]    |                         |
[INFO] [stdout]    |                         `Deserialize` is not local
[INFO] [stdout]    |                         move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_OpenMode`
[INFO] [stdout] 32 |     pub struct OpenMode: u8 {
[INFO] [stdout]    |                -------- `OpenMode` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000.rs:60:14
[INFO] [stdout]    |
[INFO] [stdout] 60 |     #[derive(Serialize, Deserialize)]
[INFO] [stdout]    |              ^--------
[INFO] [stdout]    |              |
[INFO] [stdout]    |              `Serialize` is not local
[INFO] [stdout]    |              move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_FileMode`
[INFO] [stdout] 61 |     pub struct FileMode: u32 {
[INFO] [stdout]    |                -------- `FileMode` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000.rs:60:25
[INFO] [stdout]    |
[INFO] [stdout] 60 |     #[derive(Serialize, Deserialize)]
[INFO] [stdout]    |                         ^----------
[INFO] [stdout]    |                         |
[INFO] [stdout]    |                         `Deserialize` is not local
[INFO] [stdout]    |                         move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_FileMode`
[INFO] [stdout] 61 |     pub struct FileMode: u32 {
[INFO] [stdout]    |                -------- `FileMode` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^---------------
[INFO] [stdout]     |                                            |
[INFO] [stdout]     |                                            `Serialize` is not local
[INFO] [stdout]     |                                            move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Rversion`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 141 | |      Rversion {
[INFO] [stdout]     | |      -------- `Rversion` is not local
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000.rs:94:10
[INFO] [stdout]    |
[INFO] [stdout] 94 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq, Clone)]
[INFO] [stdout]    |          ^--------
[INFO] [stdout]    |          |
[INFO] [stdout]    |          `Serialize` is not local
[INFO] [stdout]    |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Qid`
[INFO] [stdout] 95 | pub struct Qid {
[INFO] [stdout]    |            --- `Qid` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000.rs:94:21
[INFO] [stdout]    |
[INFO] [stdout] 94 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq, Clone)]
[INFO] [stdout]    |                     ^----------
[INFO] [stdout]    |                     |
[INFO] [stdout]    |                     `Deserialize` is not local
[INFO] [stdout]    |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Qid`
[INFO] [stdout] 95 | pub struct Qid {
[INFO] [stdout]    |            --- `Qid` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/p2000.rs:101:10
[INFO] [stdout]     |
[INFO] [stdout] 101 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq, Clone)]
[INFO] [stdout]     |          ^--------
[INFO] [stdout]     |          |
[INFO] [stdout]     |          `Serialize` is not local
[INFO] [stdout]     |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Stat`
[INFO] [stdout] 102 | pub struct Stat {
[INFO] [stdout]     |            ---- `Stat` is not local
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^-----------------
[INFO] [stdout]     |                        |
[INFO] [stdout]     |                        `Deserialize` is not local
[INFO] [stdout]     |                        move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Tauth`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 146 | |      Tauth {
[INFO] [stdout]     | |      ----- `Tauth` is not local
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/p2000.rs:101:21
[INFO] [stdout]     |
[INFO] [stdout] 101 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq, Clone)]
[INFO] [stdout]     |                     ^----------
[INFO] [stdout]     |                     |
[INFO] [stdout]     |                     `Deserialize` is not local
[INFO] [stdout]     |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Stat`
[INFO] [stdout] 102 | pub struct Stat {
[INFO] [stdout]     |            ---- `Stat` is not local
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]  --> src/p2000/l.rs:8:10
[INFO] [stdout]   |
[INFO] [stdout] 8 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]   |          ^--------
[INFO] [stdout]   |          |
[INFO] [stdout]   |          `Serialize` is not local
[INFO] [stdout]   |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Tauth`
[INFO] [stdout] 9 | pub struct Tauth {
[INFO] [stdout]   |            ----- `Tauth` is not local
[INFO] [stdout]   |
[INFO] [stdout]   = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]   = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]   = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]   = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]   = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]  --> src/p2000/l.rs:8:21
[INFO] [stdout]   |
[INFO] [stdout] 8 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]   |                     ^----------
[INFO] [stdout]   |                     |
[INFO] [stdout]   |                     `Deserialize` is not local
[INFO] [stdout]   |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Tauth`
[INFO] [stdout] 9 | pub struct Tauth {
[INFO] [stdout]   |            ----- `Tauth` is not local
[INFO] [stdout]   |
[INFO] [stdout]   = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]   = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]   = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]   = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]   = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000/l.rs:17:10
[INFO] [stdout]    |
[INFO] [stdout] 17 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |          ^--------
[INFO] [stdout]    |          |
[INFO] [stdout]    |          `Serialize` is not local
[INFO] [stdout]    |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Tattach`
[INFO] [stdout] 18 | pub struct Tattach {
[INFO] [stdout]    |            ------- `Tattach` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000/l.rs:17:21
[INFO] [stdout]    |
[INFO] [stdout] 17 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |                     ^----------
[INFO] [stdout]    |                     |
[INFO] [stdout]    |                     `Deserialize` is not local
[INFO] [stdout]    |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Tattach`
[INFO] [stdout] 18 | pub struct Tattach {
[INFO] [stdout]    |            ------- `Tattach` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000/l.rs:27:10
[INFO] [stdout]    |
[INFO] [stdout] 27 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |          ^--------
[INFO] [stdout]    |          |
[INFO] [stdout]    |          `Serialize` is not local
[INFO] [stdout]    |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Rlerror`
[INFO] [stdout] 28 | pub struct Rlerror {
[INFO] [stdout]    |            ------- `Rlerror` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000/l.rs:27:21
[INFO] [stdout]    |
[INFO] [stdout] 27 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |                     ^----------
[INFO] [stdout]    |                     |
[INFO] [stdout]    |                     `Deserialize` is not local
[INFO] [stdout]    |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Rlerror`
[INFO] [stdout] 28 | pub struct Rlerror {
[INFO] [stdout]    |            ------- `Rlerror` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000/l.rs:33:10
[INFO] [stdout]    |
[INFO] [stdout] 33 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |          ^--------
[INFO] [stdout]    |          |
[INFO] [stdout]    |          `Serialize` is not local
[INFO] [stdout]    |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Tstatfs`
[INFO] [stdout] 34 | pub struct Tstatfs {
[INFO] [stdout]    |            ------- `Tstatfs` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000/l.rs:33:21
[INFO] [stdout]    |
[INFO] [stdout] 33 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |                     ^----------
[INFO] [stdout]    |                     |
[INFO] [stdout]    |                     `Deserialize` is not local
[INFO] [stdout]    |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Tstatfs`
[INFO] [stdout] 34 | pub struct Tstatfs {
[INFO] [stdout]    |            ------- `Tstatfs` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000/l.rs:39:10
[INFO] [stdout]    |
[INFO] [stdout] 39 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |          ^--------
[INFO] [stdout]    |          |
[INFO] [stdout]    |          `Serialize` is not local
[INFO] [stdout]    |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Rstatfs`
[INFO] [stdout] 40 | pub struct Rstatfs {
[INFO] [stdout]    |            ------- `Rstatfs` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000/l.rs:39:21
[INFO] [stdout]    |
[INFO] [stdout] 39 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |                     ^----------
[INFO] [stdout]    |                     |
[INFO] [stdout]    |                     `Deserialize` is not local
[INFO] [stdout]    |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Rstatfs`
[INFO] [stdout] 40 | pub struct Rstatfs {
[INFO] [stdout]    |            ------- `Rstatfs` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000/l.rs:53:10
[INFO] [stdout]    |
[INFO] [stdout] 53 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |          ^--------
[INFO] [stdout]    |          |
[INFO] [stdout]    |          `Serialize` is not local
[INFO] [stdout]    |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Tlopen`
[INFO] [stdout] 54 | pub struct Tlopen {
[INFO] [stdout]    |            ------ `Tlopen` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000/l.rs:53:21
[INFO] [stdout]    |
[INFO] [stdout] 53 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |                     ^----------
[INFO] [stdout]    |                     |
[INFO] [stdout]    |                     `Deserialize` is not local
[INFO] [stdout]    |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Tlopen`
[INFO] [stdout] 54 | pub struct Tlopen {
[INFO] [stdout]    |            ------ `Tlopen` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000/l.rs:60:10
[INFO] [stdout]    |
[INFO] [stdout] 60 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |          ^--------
[INFO] [stdout]    |          |
[INFO] [stdout]    |          `Serialize` is not local
[INFO] [stdout]    |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Rlopen`
[INFO] [stdout] 61 | pub struct Rlopen {
[INFO] [stdout]    |            ------ `Rlopen` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000/l.rs:60:21
[INFO] [stdout]    |
[INFO] [stdout] 60 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |                     ^----------
[INFO] [stdout]    |                     |
[INFO] [stdout]    |                     `Deserialize` is not local
[INFO] [stdout]    |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Rlopen`
[INFO] [stdout] 61 | pub struct Rlopen {
[INFO] [stdout]    |            ------ `Rlopen` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000/l.rs:67:10
[INFO] [stdout]    |
[INFO] [stdout] 67 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |          ^--------
[INFO] [stdout]    |          |
[INFO] [stdout]    |          `Serialize` is not local
[INFO] [stdout]    |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Tlcreate`
[INFO] [stdout] 68 | pub struct Tlcreate {
[INFO] [stdout]    |            -------- `Tlcreate` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000/l.rs:67:21
[INFO] [stdout]    |
[INFO] [stdout] 67 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |                     ^----------
[INFO] [stdout]    |                     |
[INFO] [stdout]    |                     `Deserialize` is not local
[INFO] [stdout]    |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Tlcreate`
[INFO] [stdout] 68 | pub struct Tlcreate {
[INFO] [stdout]    |            -------- `Tlcreate` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000/l.rs:77:10
[INFO] [stdout]    |
[INFO] [stdout] 77 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |          ^--------
[INFO] [stdout]    |          |
[INFO] [stdout]    |          `Serialize` is not local
[INFO] [stdout]    |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Rlcreate`
[INFO] [stdout] 78 | pub struct Rlcreate {
[INFO] [stdout]    |            -------- `Rlcreate` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000/l.rs:77:21
[INFO] [stdout]    |
[INFO] [stdout] 77 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |                     ^----------
[INFO] [stdout]    |                     |
[INFO] [stdout]    |                     `Deserialize` is not local
[INFO] [stdout]    |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Rlcreate`
[INFO] [stdout] 78 | pub struct Rlcreate {
[INFO] [stdout]    |            -------- `Rlcreate` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000/l.rs:84:10
[INFO] [stdout]    |
[INFO] [stdout] 84 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |          ^--------
[INFO] [stdout]    |          |
[INFO] [stdout]    |          `Serialize` is not local
[INFO] [stdout]    |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Tsymlink`
[INFO] [stdout] 85 | pub struct Tsymlink {
[INFO] [stdout]    |            -------- `Tsymlink` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000/l.rs:84:21
[INFO] [stdout]    |
[INFO] [stdout] 84 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |                     ^----------
[INFO] [stdout]    |                     |
[INFO] [stdout]    |                     `Deserialize` is not local
[INFO] [stdout]    |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Tsymlink`
[INFO] [stdout] 85 | pub struct Tsymlink {
[INFO] [stdout]    |            -------- `Tsymlink` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000/l.rs:93:10
[INFO] [stdout]    |
[INFO] [stdout] 93 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |          ^--------
[INFO] [stdout]    |          |
[INFO] [stdout]    |          `Serialize` is not local
[INFO] [stdout]    |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Rsymlink`
[INFO] [stdout] 94 | pub struct Rsymlink {
[INFO] [stdout]    |            -------- `Rsymlink` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000/l.rs:93:21
[INFO] [stdout]    |
[INFO] [stdout] 93 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |                     ^----------
[INFO] [stdout]    |                     |
[INFO] [stdout]    |                     `Deserialize` is not local
[INFO] [stdout]    |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Rsymlink`
[INFO] [stdout] 94 | pub struct Rsymlink {
[INFO] [stdout]    |            -------- `Rsymlink` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/p2000/l.rs:99:10
[INFO] [stdout]     |
[INFO] [stdout]  99 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |          ^--------
[INFO] [stdout]     |          |
[INFO] [stdout]     |          `Serialize` is not local
[INFO] [stdout]     |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Tmknod`
[INFO] [stdout] 100 | pub struct Tmknod {
[INFO] [stdout]     |            ------ `Tmknod` is not local
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/p2000/l.rs:99:21
[INFO] [stdout]     |
[INFO] [stdout]  99 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |                     ^----------
[INFO] [stdout]     |                     |
[INFO] [stdout]     |                     `Deserialize` is not local
[INFO] [stdout]     |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Tmknod`
[INFO] [stdout] 100 | pub struct Tmknod {
[INFO] [stdout]     |            ------ `Tmknod` is not local
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/p2000/l.rs:110:10
[INFO] [stdout]     |
[INFO] [stdout] 110 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |          ^--------
[INFO] [stdout]     |          |
[INFO] [stdout]     |          `Serialize` is not local
[INFO] [stdout]     |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Rmknod`
[INFO] [stdout] 111 | pub struct Rmknod {
[INFO] [stdout]     |            ------ `Rmknod` is not local
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/p2000/l.rs:110:21
[INFO] [stdout]     |
[INFO] [stdout] 110 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |                     ^----------
[INFO] [stdout]     |                     |
[INFO] [stdout]     |                     `Deserialize` is not local
[INFO] [stdout]     |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Rmknod`
[INFO] [stdout] 111 | pub struct Rmknod {
[INFO] [stdout]     |            ------ `Rmknod` is not local
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/p2000/l.rs:116:10
[INFO] [stdout]     |
[INFO] [stdout] 116 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |          ^--------
[INFO] [stdout]     |          |
[INFO] [stdout]     |          `Serialize` is not local
[INFO] [stdout]     |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Trename`
[INFO] [stdout] 117 | pub struct Trename {
[INFO] [stdout]     |            ------- `Trename` is not local
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/p2000/l.rs:116:21
[INFO] [stdout]     |
[INFO] [stdout] 116 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |                     ^----------
[INFO] [stdout]     |                     |
[INFO] [stdout]     |                     `Deserialize` is not local
[INFO] [stdout]     |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Trename`
[INFO] [stdout] 117 | pub struct Trename {
[INFO] [stdout]     |            ------- `Trename` is not local
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/p2000/l.rs:124:10
[INFO] [stdout]     |
[INFO] [stdout] 124 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |          ^--------
[INFO] [stdout]     |          |
[INFO] [stdout]     |          `Serialize` is not local
[INFO] [stdout]     |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Rrename`
[INFO] [stdout] 125 | pub struct Rrename {
[INFO] [stdout]     |            ------- `Rrename` is not local
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/p2000/l.rs:124:21
[INFO] [stdout]     |
[INFO] [stdout] 124 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |                     ^----------
[INFO] [stdout]     |                     |
[INFO] [stdout]     |                     `Deserialize` is not local
[INFO] [stdout]     |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Rrename`
[INFO] [stdout] 125 | pub struct Rrename {
[INFO] [stdout]     |            ------- `Rrename` is not local
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/p2000/l.rs:129:10
[INFO] [stdout]     |
[INFO] [stdout] 129 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |          ^--------
[INFO] [stdout]     |          |
[INFO] [stdout]     |          `Serialize` is not local
[INFO] [stdout]     |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Treadlink`
[INFO] [stdout] 130 | pub struct Treadlink {
[INFO] [stdout]     |            --------- `Treadlink` is not local
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/p2000/l.rs:129:21
[INFO] [stdout]     |
[INFO] [stdout] 129 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |                     ^----------
[INFO] [stdout]     |                     |
[INFO] [stdout]     |                     `Deserialize` is not local
[INFO] [stdout]     |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Treadlink`
[INFO] [stdout] 130 | pub struct Treadlink {
[INFO] [stdout]     |            --------- `Treadlink` is not local
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/p2000/l.rs:135:10
[INFO] [stdout]     |
[INFO] [stdout] 135 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |          ^--------
[INFO] [stdout]     |          |
[INFO] [stdout]     |          `Serialize` is not local
[INFO] [stdout]     |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Rreadlink`
[INFO] [stdout] 136 | pub struct Rreadlink {
[INFO] [stdout]     |            --------- `Rreadlink` is not local
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/p2000/l.rs:135:21
[INFO] [stdout]     |
[INFO] [stdout] 135 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |                     ^----------
[INFO] [stdout]     |                     |
[INFO] [stdout]     |                     `Deserialize` is not local
[INFO] [stdout]     |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Rreadlink`
[INFO] [stdout] 136 | pub struct Rreadlink {
[INFO] [stdout]     |            --------- `Rreadlink` is not local
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/p2000/l.rs:141:10
[INFO] [stdout]     |
[INFO] [stdout] 141 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |          ^--------
[INFO] [stdout]     |          |
[INFO] [stdout]     |          `Serialize` is not local
[INFO] [stdout]     |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Tgetattr`
[INFO] [stdout] 142 | pub struct Tgetattr {
[INFO] [stdout]     |            -------- `Tgetattr` is not local
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/p2000/l.rs:141:21
[INFO] [stdout]     |
[INFO] [stdout] 141 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |                     ^----------
[INFO] [stdout]     |                     |
[INFO] [stdout]     |                     `Deserialize` is not local
[INFO] [stdout]     |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Tgetattr`
[INFO] [stdout] 142 | pub struct Tgetattr {
[INFO] [stdout]     |            -------- `Tgetattr` is not local
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/p2000/l.rs:149:10
[INFO] [stdout]     |
[INFO] [stdout] 149 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |          ^--------
[INFO] [stdout]     |          |
[INFO] [stdout]     |          `Serialize` is not local
[INFO] [stdout]     |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Rgetattr`
[INFO] [stdout] 150 | pub struct Rgetattr {
[INFO] [stdout]     |            -------- `Rgetattr` is not local
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/p2000/l.rs:149:21
[INFO] [stdout]     |
[INFO] [stdout] 149 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |                     ^----------
[INFO] [stdout]     |                     |
[INFO] [stdout]     |                     `Deserialize` is not local
[INFO] [stdout]     |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Rgetattr`
[INFO] [stdout] 150 | pub struct Rgetattr {
[INFO] [stdout]     |            -------- `Rgetattr` is not local
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/p2000/l.rs:179:10
[INFO] [stdout]     |
[INFO] [stdout] 179 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |          ^--------
[INFO] [stdout]     |          |
[INFO] [stdout]     |          `Serialize` is not local
[INFO] [stdout]     |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Tsetattr`
[INFO] [stdout] 180 | pub struct Tsetattr {
[INFO] [stdout]     |            -------- `Tsetattr` is not local
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/p2000/l.rs:179:21
[INFO] [stdout]     |
[INFO] [stdout] 179 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |                     ^----------
[INFO] [stdout]     |                     |
[INFO] [stdout]     |                     `Deserialize` is not local
[INFO] [stdout]     |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Tsetattr`
[INFO] [stdout] 180 | pub struct Tsetattr {
[INFO] [stdout]     |            -------- `Tsetattr` is not local
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/p2000/l.rs:194:10
[INFO] [stdout]     |
[INFO] [stdout] 194 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |          ^--------
[INFO] [stdout]     |          |
[INFO] [stdout]     |          `Serialize` is not local
[INFO] [stdout]     |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Rsetattr`
[INFO] [stdout] 195 | pub struct Rsetattr {
[INFO] [stdout]     |            -------- `Rsetattr` is not local
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/p2000/l.rs:194:21
[INFO] [stdout]     |
[INFO] [stdout] 194 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]     |                     ^----------
[INFO] [stdout]     |                     |
[INFO] [stdout]     |                     `Deserialize` is not local
[INFO] [stdout]     |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Rsetattr`
[INFO] [stdout] 195 | pub struct Rsetattr {
[INFO] [stdout]     |            -------- `Rsetattr` is not local
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]  --> src/p2000/u.rs:8:10
[INFO] [stdout]   |
[INFO] [stdout] 8 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]   |          ^--------
[INFO] [stdout]   |          |
[INFO] [stdout]   |          `Serialize` is not local
[INFO] [stdout]   |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Topenfd`
[INFO] [stdout] 9 | pub struct Topenfd {
[INFO] [stdout]   |            ------- `Topenfd` is not local
[INFO] [stdout]   |
[INFO] [stdout]   = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]   = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]   = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]   = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]   = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]  --> src/p2000/u.rs:8:21
[INFO] [stdout]   |
[INFO] [stdout] 8 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]   |                     ^----------
[INFO] [stdout]   |                     |
[INFO] [stdout]   |                     `Deserialize` is not local
[INFO] [stdout]   |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Topenfd`
[INFO] [stdout] 9 | pub struct Topenfd {
[INFO] [stdout]   |            ------- `Topenfd` is not local
[INFO] [stdout]   |
[INFO] [stdout]   = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]   = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]   = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]   = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]   = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000/u.rs:15:10
[INFO] [stdout]    |
[INFO] [stdout] 15 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |          ^--------
[INFO] [stdout]    |          |
[INFO] [stdout]    |          `Serialize` is not local
[INFO] [stdout]    |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Ropenfd`
[INFO] [stdout] 16 | pub struct Ropenfd {
[INFO] [stdout]    |            ------- `Ropenfd` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/p2000/u.rs:15:21
[INFO] [stdout]    |
[INFO] [stdout] 15 | #[derive(Serialize, Deserialize, Debug, PartialEq, Eq)]
[INFO] [stdout]    |                     ^----------
[INFO] [stdout]    |                     |
[INFO] [stdout]    |                     `Deserialize` is not local
[INFO] [stdout]    |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Ropenfd`
[INFO] [stdout] 16 | pub struct Ropenfd {
[INFO] [stdout]    |            ------- `Ropenfd` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^-----------------
[INFO] [stdout]     |                        |
[INFO] [stdout]     |                        `Deserialize` is not local
[INFO] [stdout]     |                        move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Tversion`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout]     | |      -------- `Tversion` is not local
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^---------------
[INFO] [stdout]     |                                            |
[INFO] [stdout]     |                                            `Serialize` is not local
[INFO] [stdout]     |                                            move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Tauth`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 146 | |      Tauth {
[INFO] [stdout]     | |      ----- `Tauth` is not local
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^-----------------
[INFO] [stdout]     |                        |
[INFO] [stdout]     |                        `Deserialize` is not local
[INFO] [stdout]     |                        move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Rauth`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 152 | |      Rauth {
[INFO] [stdout]     | |      ----- `Rauth` is not local
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^---------------
[INFO] [stdout]     |                                            |
[INFO] [stdout]     |                                            `Serialize` is not local
[INFO] [stdout]     |                                            move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Rauth`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 152 | |      Rauth {
[INFO] [stdout]     | |      ----- `Rauth` is not local
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^---------------
[INFO] [stdout]     |                                            |
[INFO] [stdout]     |                                            `Serialize` is not local
[INFO] [stdout]     |                                            move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Tversion`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout]     | |      -------- `Tversion` is not local
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^-----------------
[INFO] [stdout]     |                        |
[INFO] [stdout]     |                        `Deserialize` is not local
[INFO] [stdout]     |                        move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Rversion`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 141 | |      Rversion {
[INFO] [stdout]     | |      -------- `Rversion` is not local
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^---------------
[INFO] [stdout]     |                                            |
[INFO] [stdout]     |                                            `Serialize` is not local
[INFO] [stdout]     |                                            move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Rversion`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 141 | |      Rversion {
[INFO] [stdout]     | |      -------- `Rversion` is not local
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^-----------------
[INFO] [stdout]     |                        |
[INFO] [stdout]     |                        `Deserialize` is not local
[INFO] [stdout]     |                        move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Tauth`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 146 | |      Tauth {
[INFO] [stdout]     | |      ----- `Tauth` is not local
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^-----------------
[INFO] [stdout]     |                        |
[INFO] [stdout]     |                        `Deserialize` is not local
[INFO] [stdout]     |                        move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Rerror`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 156 | |      Rerror {
[INFO] [stdout]     | |      ------ `Rerror` is not local
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^---------------
[INFO] [stdout]     |                                            |
[INFO] [stdout]     |                                            `Serialize` is not local
[INFO] [stdout]     |                                            move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Tauth`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 146 | |      Tauth {
[INFO] [stdout]     | |      ----- `Tauth` is not local
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^-----------------
[INFO] [stdout]     |                        |
[INFO] [stdout]     |                        `Deserialize` is not local
[INFO] [stdout]     |                        move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Rauth`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 152 | |      Rauth {
[INFO] [stdout]     | |      ----- `Rauth` is not local
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^---------------
[INFO] [stdout]     |                                            |
[INFO] [stdout]     |                                            `Serialize` is not local
[INFO] [stdout]     |                                            move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Rerror`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 156 | |      Rerror {
[INFO] [stdout]     | |      ------ `Rerror` is not local
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^-----------------
[INFO] [stdout]     |                        |
[INFO] [stdout]     |                        `Deserialize` is not local
[INFO] [stdout]     |                        move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Tflush`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 160 | |      Tflush {
[INFO] [stdout]     | |      ------ `Tflush` is not local
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^---------------
[INFO] [stdout]     |                                            |
[INFO] [stdout]     |                                            `Serialize` is not local
[INFO] [stdout]     |                                            move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Rauth`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 152 | |      Rauth {
[INFO] [stdout]     | |      ----- `Rauth` is not local
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^-----------------
[INFO] [stdout]     |                        |
[INFO] [stdout]     |                        `Deserialize` is not local
[INFO] [stdout]     |                        move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Rerror`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 156 | |      Rerror {
[INFO] [stdout]     | |      ------ `Rerror` is not local
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^---------------
[INFO] [stdout]     |                                            |
[INFO] [stdout]     |                                            `Serialize` is not local
[INFO] [stdout]     |                                            move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Tflush`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 160 | |      Tflush {
[INFO] [stdout]     | |      ------ `Tflush` is not local
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^-----------------
[INFO] [stdout]     |                        |
[INFO] [stdout]     |                        `Deserialize` is not local
[INFO] [stdout]     |                        move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Rflush`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 163 | |      Rflush {
[INFO] [stdout]     | |      ------ `Rflush` is not local
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^---------------
[INFO] [stdout]     |                                            |
[INFO] [stdout]     |                                            `Serialize` is not local
[INFO] [stdout]     |                                            move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Rerror`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 156 | |      Rerror {
[INFO] [stdout]     | |      ------ `Rerror` is not local
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^-----------------
[INFO] [stdout]     |                        |
[INFO] [stdout]     |                        `Deserialize` is not local
[INFO] [stdout]     |                        move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Tflush`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 160 | |      Tflush {
[INFO] [stdout]     | |      ------ `Tflush` is not local
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^---------------
[INFO] [stdout]     |                                            |
[INFO] [stdout]     |                                            `Serialize` is not local
[INFO] [stdout]     |                                            move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Rflush`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 163 | |      Rflush {
[INFO] [stdout]     | |      ------ `Rflush` is not local
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^---------------
[INFO] [stdout]     |                                            |
[INFO] [stdout]     |                                            `Serialize` is not local
[INFO] [stdout]     |                                            move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Tflush`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 160 | |      Tflush {
[INFO] [stdout]     | |      ------ `Tflush` is not local
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^-----------------
[INFO] [stdout]     |                        |
[INFO] [stdout]     |                        `Deserialize` is not local
[INFO] [stdout]     |                        move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Tattach`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 166 | |      Tattach {
[INFO] [stdout]     | |      ------- `Tattach` is not local
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^-----------------
[INFO] [stdout]     |                        |
[INFO] [stdout]     |                        `Deserialize` is not local
[INFO] [stdout]     |                        move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Rflush`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 163 | |      Rflush {
[INFO] [stdout]     | |      ------ `Rflush` is not local
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^---------------
[INFO] [stdout]     |                                            |
[INFO] [stdout]     |                                            `Serialize` is not local
[INFO] [stdout]     |                                            move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Tattach`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 166 | |      Tattach {
[INFO] [stdout]     | |      ------- `Tattach` is not local
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^-----------------
[INFO] [stdout]     |                        |
[INFO] [stdout]     |                        `Deserialize` is not local
[INFO] [stdout]     |                        move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Rattach`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 173 | |      Rattach {
[INFO] [stdout]     | |      ------- `Rattach` is not local
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^---------------
[INFO] [stdout]     |                                            |
[INFO] [stdout]     |                                            `Serialize` is not local
[INFO] [stdout]     |                                            move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Rflush`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 163 | |      Rflush {
[INFO] [stdout]     | |      ------ `Rflush` is not local
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^---------------
[INFO] [stdout]     |                                            |
[INFO] [stdout]     |                                            `Serialize` is not local
[INFO] [stdout]     |                                            move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Rattach`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 173 | |      Rattach {
[INFO] [stdout]     | |      ------- `Rattach` is not local
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^-----------------
[INFO] [stdout]     |                        |
[INFO] [stdout]     |                        `Deserialize` is not local
[INFO] [stdout]     |                        move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Tattach`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 166 | |      Tattach {
[INFO] [stdout]     | |      ------- `Tattach` is not local
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^-----------------
[INFO] [stdout]     |                        |
[INFO] [stdout]     |                        `Deserialize` is not local
[INFO] [stdout]     |                        move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Twalk`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 177 | |      Twalk {
[INFO] [stdout]     | |      ----- `Twalk` is not local
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^---------------
[INFO] [stdout]     |                                            |
[INFO] [stdout]     |                                            `Serialize` is not local
[INFO] [stdout]     |                                            move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Tattach`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 166 | |      Tattach {
[INFO] [stdout]     | |      ------- `Tattach` is not local
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^---------------
[INFO] [stdout]     |                                            |
[INFO] [stdout]     |                                            `Serialize` is not local
[INFO] [stdout]     |                                            move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Twalk`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 177 | |      Twalk {
[INFO] [stdout]     | |      ----- `Twalk` is not local
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^-----------------
[INFO] [stdout]     |                        |
[INFO] [stdout]     |                        `Deserialize` is not local
[INFO] [stdout]     |                        move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Rattach`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 173 | |      Rattach {
[INFO] [stdout]     | |      ------- `Rattach` is not local
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^-----------------
[INFO] [stdout]     |                        |
[INFO] [stdout]     |                        `Deserialize` is not local
[INFO] [stdout]     |                        move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Rwalk`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 183 | |      Rwalk {
[INFO] [stdout]     | |      ----- `Rwalk` is not local
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^---------------
[INFO] [stdout]     |                                            |
[INFO] [stdout]     |                                            `Serialize` is not local
[INFO] [stdout]     |                                            move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Rattach`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 173 | |      Rattach {
[INFO] [stdout]     | |      ------- `Rattach` is not local
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^-----------------
[INFO] [stdout]     |                        |
[INFO] [stdout]     |                        `Deserialize` is not local
[INFO] [stdout]     |                        move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Twalk`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 177 | |      Twalk {
[INFO] [stdout]     | |      ----- `Twalk` is not local
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^---------------
[INFO] [stdout]     |                                            |
[INFO] [stdout]     |                                            `Serialize` is not local
[INFO] [stdout]     |                                            move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Rwalk`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 183 | |      Rwalk {
[INFO] [stdout]     | |      ----- `Rwalk` is not local
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^-----------------
[INFO] [stdout]     |                        |
[INFO] [stdout]     |                        `Deserialize` is not local
[INFO] [stdout]     |                        move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Topen`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 187 | |      Topen {
[INFO] [stdout]     | |      ----- `Topen` is not local
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^---------------
[INFO] [stdout]     |                                            |
[INFO] [stdout]     |                                            `Serialize` is not local
[INFO] [stdout]     |                                            move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Twalk`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 177 | |      Twalk {
[INFO] [stdout]     | |      ----- `Twalk` is not local
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^---------------
[INFO] [stdout]     |                                            |
[INFO] [stdout]     |                                            `Serialize` is not local
[INFO] [stdout]     |                                            move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Topen`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 187 | |      Topen {
[INFO] [stdout]     | |      ----- `Topen` is not local
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^-----------------
[INFO] [stdout]     |                        |
[INFO] [stdout]     |                        `Deserialize` is not local
[INFO] [stdout]     |                        move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Rwalk`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 183 | |      Rwalk {
[INFO] [stdout]     | |      ----- `Rwalk` is not local
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^-----------------
[INFO] [stdout]     |                        |
[INFO] [stdout]     |                        `Deserialize` is not local
[INFO] [stdout]     |                        move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Ropen`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 192 | |      Ropen {
[INFO] [stdout]     | |      ----- `Ropen` is not local
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^---------------
[INFO] [stdout]     |                                            |
[INFO] [stdout]     |                                            `Serialize` is not local
[INFO] [stdout]     |                                            move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Rwalk`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 183 | |      Rwalk {
[INFO] [stdout]     | |      ----- `Rwalk` is not local
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^---------------
[INFO] [stdout]     |                                            |
[INFO] [stdout]     |                                            `Serialize` is not local
[INFO] [stdout]     |                                            move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Ropen`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 192 | |      Ropen {
[INFO] [stdout]     | |      ----- `Ropen` is not local
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^-----------------
[INFO] [stdout]     |                        |
[INFO] [stdout]     |                        `Deserialize` is not local
[INFO] [stdout]     |                        move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Topen`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 187 | |      Topen {
[INFO] [stdout]     | |      ----- `Topen` is not local
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:42
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                                            ^---------------
[INFO] [stdout]     |                                            |
[INFO] [stdout]     |                                            `Serialize` is not local
[INFO] [stdout]     |                                            move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Topen`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 187 | |      Topen {
[INFO] [stdout]     | |      ----- `Topen` is not local
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Serialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/message.rs:53:22
[INFO] [stdout]     |
[INFO] [stdout]  53 |               #[derive(serde::Deserialize, serde::Serialize)]
[INFO] [stdout]     |                        ^-----------------
[INFO] [stdout]     |                        |
[INFO] [stdout]     |                        `Deserialize` is not local
[INFO] [stdout]     |                        move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Tcreate`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/p2000.rs:134:1
[INFO] [stdout]     |
[INFO] [stdout] 134 | / crate::messages! {
[INFO] [stdout] 135 | |     #[derive(Debug, PartialEq, Eq)]
[INFO] [stdout] 136 | |      Tversion {
[INFO] [stdout] 137 | |         msize: u32,
[INFO] [stdout] ...   |
[INFO] [stdout] 197 | |      Tcreate {
[INFO] [stdout]     | |      ------- `Tcreate` is not local
[INFO] [stdout] ...   |
[INFO] [stdout] 267 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: the derive macro `serde::Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the derive macro `serde::Deserialize` which comes from the expansion of the macro `crate::messages` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[WARN] too many lines in the log, truncating it
