[INFO] cloning repository https://github.com/vi/mal-rust-vi [INFO] running `Command { std: "git" "-c" "credential.helper=" "-c" "credential.helper=/workspace/cargo-home/bin/git-credential-null" "clone" "--bare" "https://github.com/vi/mal-rust-vi" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fvi%2Fmal-rust-vi", kill_on_drop: false }` [INFO] [stderr] Cloning into bare repository '/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fvi%2Fmal-rust-vi'... [INFO] running `Command { std: "git" "rev-parse" "HEAD", kill_on_drop: false }` [INFO] [stdout] 9614838720bc130d49d7a15777e6a1f73b13ca25 [INFO] checking vi/mal-rust-vi against try#121a90d34197f711021eeb158e7f4184b8be8ceb for pr-140313 [INFO] running `Command { std: "git" "clone" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fvi%2Fmal-rust-vi" "/workspace/builds/worker-6-tc2/source", kill_on_drop: false }` [INFO] [stderr] Cloning into '/workspace/builds/worker-6-tc2/source'... [INFO] [stderr] done. [INFO] validating manifest of git repo https://github.com/vi/mal-rust-vi on toolchain 121a90d34197f711021eeb158e7f4184b8be8ceb [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+121a90d34197f711021eeb158e7f4184b8be8ceb" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] started tweaking git repo https://github.com/vi/mal-rust-vi [INFO] finished tweaking git repo https://github.com/vi/mal-rust-vi [INFO] tweaked toml for git repo https://github.com/vi/mal-rust-vi written to /workspace/builds/worker-6-tc2/source/Cargo.toml [INFO] crate git repo https://github.com/vi/mal-rust-vi 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" "+121a90d34197f711021eeb158e7f4184b8be8ceb" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/source:/opt/rustwide/workdir:ro,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" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:b0b074c097205a61b89e8ad263052f976b2b332c4dc5f02aef1fe52501660d6e" "/opt/rustwide/cargo-home/bin/cargo" "+121a90d34197f711021eeb158e7f4184b8be8ceb" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] e12e4dae02f0fc7537b7fdce23f0b4b9771f4205ef562d2b2888e6c6c726b27a [INFO] running `Command { std: "docker" "start" "-a" "e12e4dae02f0fc7537b7fdce23f0b4b9771f4205ef562d2b2888e6c6c726b27a", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "e12e4dae02f0fc7537b7fdce23f0b4b9771f4205ef562d2b2888e6c6c726b27a", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "e12e4dae02f0fc7537b7fdce23f0b4b9771f4205ef562d2b2888e6c6c726b27a", kill_on_drop: false }` [INFO] [stdout] e12e4dae02f0fc7537b7fdce23f0b4b9771f4205ef562d2b2888e6c6c726b27a [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/source:/opt/rustwide/workdir:ro,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" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-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" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:b0b074c097205a61b89e8ad263052f976b2b332c4dc5f02aef1fe52501660d6e" "/opt/rustwide/cargo-home/bin/cargo" "+121a90d34197f711021eeb158e7f4184b8be8ceb" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] 6ec94b8984aa6f14ca943d5625139f86cecc033439821138f66a10d0e8c743d3 [INFO] running `Command { std: "docker" "start" "-a" "6ec94b8984aa6f14ca943d5625139f86cecc033439821138f66a10d0e8c743d3", kill_on_drop: false }` [INFO] [stderr] Compiling proc-macro2 v0.4.20 [INFO] [stderr] Compiling cc v1.0.25 [INFO] [stderr] Compiling failure_derive v0.1.2 [INFO] [stderr] Compiling libc v0.2.43 [INFO] [stderr] Compiling cfg-if v0.1.5 [INFO] [stderr] Compiling rustc-demangle v0.1.9 [INFO] [stderr] Compiling ucd-trie v0.1.1 [INFO] [stderr] Compiling maplit v1.0.1 [INFO] [stderr] Compiling either v1.5.0 [INFO] [stderr] Compiling itertools v0.7.8 [INFO] [stderr] Compiling pest v2.0.1 [INFO] [stderr] Checking slab v0.4.1 [INFO] [stderr] Checking slab_typesafe v0.1.2 [INFO] [stderr] Compiling semver-parser v0.7.0 [INFO] [stderr] Compiling backtrace-sys v0.1.24 [INFO] [stderr] Compiling typenum v1.10.0 [INFO] [stderr] Compiling semver v0.9.0 [INFO] [stderr] Checking unescape v0.1.0 [INFO] [stderr] Compiling rustc_version v0.2.3 [INFO] [stderr] Compiling quote v0.6.8 [INFO] [stderr] Checking malvi_step0 v0.1.0 (/opt/rustwide/workdir/step0) [INFO] [stderr] Compiling im-rc v12.2.0 [INFO] [stderr] Compiling syn v0.14.9 [INFO] [stderr] Compiling syn v0.15.11 [INFO] [stderr] Compiling pest_meta v2.0.3 [INFO] [stderr] Compiling backtrace v0.3.9 [INFO] [stderr] Compiling synstructure v0.9.0 [INFO] [stderr] Compiling pest_generator v2.0.0 [INFO] [stderr] Compiling pest_derive v2.0.1 [INFO] [stderr] Compiling failure v0.1.2 [INFO] [stderr] Compiling single v1.0.0 [INFO] [stderr] Compiling pest-deconstruct-derive v0.2.0 [INFO] [stderr] Checking pest-deconstruct v0.2.0 [INFO] [stderr] Checking malvi_step7 v0.1.0 (/opt/rustwide/workdir/step7) [INFO] [stderr] Checking malvi_step3b v0.1.0 (/opt/rustwide/workdir/step3b) [INFO] [stderr] Checking malvi_step8 v0.1.0 (/opt/rustwide/workdir/step8) [INFO] [stderr] Checking malvi_stepA v0.1.0 (/opt/rustwide/workdir/stepA) [INFO] [stderr] Checking malvi_step3c v0.1.0 (/opt/rustwide/workdir/step3c) [INFO] [stderr] Checking malvi_step3d v0.1.0 (/opt/rustwide/workdir/step3d) [INFO] [stderr] Checking malvi_step9 v0.1.0 (/opt/rustwide/workdir/step9) [INFO] [stderr] Checking malvi_step4 v0.1.0 (/opt/rustwide/workdir/step4) [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step3b/src/parse.rs:17:21 [INFO] [stdout] | [INFO] [stdout] 17 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see 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 `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step3b/src/parse.rs:25:21 [INFO] [stdout] | [INFO] [stdout] 25 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step3b/src/parse.rs:31:21 [INFO] [stdout] | [INFO] [stdout] 31 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step3b/src/parse.rs:37:21 [INFO] [stdout] | [INFO] [stdout] 37 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step3b/src/parse.rs:43:21 [INFO] [stdout] | [INFO] [stdout] 43 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step3b/src/parse.rs:49:21 [INFO] [stdout] | [INFO] [stdout] 49 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step3b/src/parse.rs:56:21 [INFO] [stdout] | [INFO] [stdout] 56 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step3b/src/parse.rs:63:21 [INFO] [stdout] | [INFO] [stdout] 63 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step3b/src/parse.rs:70:21 [INFO] [stdout] | [INFO] [stdout] 70 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step3b/src/parse.rs:77:21 [INFO] [stdout] | [INFO] [stdout] 77 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step3b/src/parse.rs:84:21 [INFO] [stdout] | [INFO] [stdout] 84 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step3b/src/parse.rs:92:21 [INFO] [stdout] | [INFO] [stdout] 92 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step3b/src/parse.rs:99:21 [INFO] [stdout] | [INFO] [stdout] 99 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step3b/src/parse.rs:106:21 [INFO] [stdout] | [INFO] [stdout] 106 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step3b/src/parse.rs:114:21 [INFO] [stdout] | [INFO] [stdout] 114 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step3b/src/parse.rs:121:21 [INFO] [stdout] | [INFO] [stdout] 121 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step3b/src/parse.rs:131:21 [INFO] [stdout] | [INFO] [stdout] 131 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step8/src/parse.rs:20:21 [INFO] [stdout] | [INFO] [stdout] 20 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see 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 `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step8/src/parse.rs:28:21 [INFO] [stdout] | [INFO] [stdout] 28 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step8/src/parse.rs:34:21 [INFO] [stdout] | [INFO] [stdout] 34 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step8/src/parse.rs:40:21 [INFO] [stdout] | [INFO] [stdout] 40 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step8/src/parse.rs:46:21 [INFO] [stdout] | [INFO] [stdout] 46 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step8/src/parse.rs:52:21 [INFO] [stdout] | [INFO] [stdout] 52 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step8/src/parse.rs:59:21 [INFO] [stdout] | [INFO] [stdout] 59 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step8/src/parse.rs:66:21 [INFO] [stdout] | [INFO] [stdout] 66 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step8/src/parse.rs:73:21 [INFO] [stdout] | [INFO] [stdout] 73 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step8/src/parse.rs:80:21 [INFO] [stdout] | [INFO] [stdout] 80 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step3c/src/parse.rs:17:21 [INFO] [stdout] | [INFO] [stdout] 17 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see 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 `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step3c/src/parse.rs:25:21 [INFO] [stdout] | [INFO] [stdout] 25 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step3c/src/parse.rs:31:21 [INFO] [stdout] | [INFO] [stdout] 31 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step3c/src/parse.rs:37:21 [INFO] [stdout] | [INFO] [stdout] 37 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step3c/src/parse.rs:43:21 [INFO] [stdout] | [INFO] [stdout] 43 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step3c/src/parse.rs:49:21 [INFO] [stdout] | [INFO] [stdout] 49 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step3c/src/parse.rs:56:21 [INFO] [stdout] | [INFO] [stdout] 56 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step3c/src/parse.rs:63:21 [INFO] [stdout] | [INFO] [stdout] 63 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step3c/src/parse.rs:70:21 [INFO] [stdout] | [INFO] [stdout] 70 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step3c/src/parse.rs:77:21 [INFO] [stdout] | [INFO] [stdout] 77 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step8/src/parse.rs:87:21 [INFO] [stdout] | [INFO] [stdout] 87 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step3c/src/parse.rs:84:21 [INFO] [stdout] | [INFO] [stdout] 84 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the feature `chunks_exact` has been stable since 1.31.0 and no longer requires an attribute to enable [INFO] [stdout] --> step3b/src/lib.rs:3:12 [INFO] [stdout] | [INFO] [stdout] 3 | #![feature(chunks_exact)] [INFO] [stdout] | ^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(stable_features)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the feature `convert_id` has been stable since 1.33.0 and no longer requires an attribute to enable [INFO] [stdout] --> step3b/src/lib.rs:2:12 [INFO] [stdout] | [INFO] [stdout] 2 | #![feature(convert_id)] [INFO] [stdout] | ^^^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: trait objects without an explicit `dyn` are deprecated [INFO] [stdout] --> step3b/src/lib.rs:78:16 [INFO] [stdout] | [INFO] [stdout] 78 | type Func = Rc]) -> Result>; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this is accepted in the current edition (Rust 2018) but is a hard error in Rust 2021! [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: `#[warn(bare_trait_objects)]` on by default [INFO] [stdout] help: if this is a dyn-compatible trait, use `dyn` [INFO] [stdout] | [INFO] [stdout] 78 | type Func = Rc]) -> Result>; [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step9/src/parse.rs:20:21 [INFO] [stdout] | [INFO] [stdout] 20 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see 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 `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step3d/src/parse.rs:18:21 [INFO] [stdout] | [INFO] [stdout] 18 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see 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 `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step4/src/parse.rs:20:21 [INFO] [stdout] | [INFO] [stdout] 20 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see 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 `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step4/src/parse.rs:28:21 [INFO] [stdout] | [INFO] [stdout] 28 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step4/src/parse.rs:34:21 [INFO] [stdout] | [INFO] [stdout] 34 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step4/src/parse.rs:40:21 [INFO] [stdout] | [INFO] [stdout] 40 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step4/src/parse.rs:46:21 [INFO] [stdout] | [INFO] [stdout] 46 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step4/src/parse.rs:52:21 [INFO] [stdout] | [INFO] [stdout] 52 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step4/src/parse.rs:59:21 [INFO] [stdout] | [INFO] [stdout] 59 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step4/src/parse.rs:66:21 [INFO] [stdout] | [INFO] [stdout] 66 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step4/src/parse.rs:73:21 [INFO] [stdout] | [INFO] [stdout] 73 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step4/src/parse.rs:80:21 [INFO] [stdout] | [INFO] [stdout] 80 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step4/src/parse.rs:87:21 [INFO] [stdout] | [INFO] [stdout] 87 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step4/src/parse.rs:95:21 [INFO] [stdout] | [INFO] [stdout] 95 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step4/src/parse.rs:102:21 [INFO] [stdout] | [INFO] [stdout] 102 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step4/src/parse.rs:109:21 [INFO] [stdout] | [INFO] [stdout] 109 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step4/src/parse.rs:117:21 [INFO] [stdout] | [INFO] [stdout] 117 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step4/src/parse.rs:124:21 [INFO] [stdout] | [INFO] [stdout] 124 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step4/src/parse.rs:134:21 [INFO] [stdout] | [INFO] [stdout] 134 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step4/src/parse.rs:149:21 [INFO] [stdout] | [INFO] [stdout] 149 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the feature `convert_id` has been stable since 1.33.0 and no longer requires an attribute to enable [INFO] [stdout] --> step4/src/lib.rs:2:12 [INFO] [stdout] | [INFO] [stdout] 2 | #![feature(convert_id)] [INFO] [stdout] | ^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(stable_features)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the feature `str_escape` has been stable since 1.34.0 and no longer requires an attribute to enable [INFO] [stdout] --> step4/src/lib.rs:3:12 [INFO] [stdout] | [INFO] [stdout] 3 | #![feature(str_escape)] [INFO] [stdout] | ^^^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: trait objects without an explicit `dyn` are deprecated [INFO] [stdout] --> step4/src/lib.rs:113:16 [INFO] [stdout] | [INFO] [stdout] 113 | type Func = Rc>) -> Result>; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this is accepted in the current edition (Rust 2018) but is a hard error in Rust 2021! [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: `#[warn(bare_trait_objects)]` on by default [INFO] [stdout] help: if this is a dyn-compatible trait, use `dyn` [INFO] [stdout] | [INFO] [stdout] 113 | type Func = Rc>) -> Result>; [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step7/src/parse.rs:20:21 [INFO] [stdout] | [INFO] [stdout] 20 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see 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 `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step7/src/parse.rs:28:21 [INFO] [stdout] | [INFO] [stdout] 28 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step7/src/parse.rs:34:21 [INFO] [stdout] | [INFO] [stdout] 34 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step7/src/parse.rs:40:21 [INFO] [stdout] | [INFO] [stdout] 40 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step7/src/parse.rs:46:21 [INFO] [stdout] | [INFO] [stdout] 46 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step7/src/parse.rs:52:21 [INFO] [stdout] | [INFO] [stdout] 52 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step7/src/parse.rs:59:21 [INFO] [stdout] | [INFO] [stdout] 59 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step7/src/parse.rs:66:21 [INFO] [stdout] | [INFO] [stdout] 66 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step7/src/parse.rs:73:21 [INFO] [stdout] | [INFO] [stdout] 73 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step7/src/parse.rs:80:21 [INFO] [stdout] | [INFO] [stdout] 80 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step7/src/parse.rs:87:21 [INFO] [stdout] | [INFO] [stdout] 87 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step7/src/parse.rs:95:21 [INFO] [stdout] | [INFO] [stdout] 95 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step7/src/parse.rs:102:21 [INFO] [stdout] | [INFO] [stdout] 102 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step7/src/parse.rs:109:21 [INFO] [stdout] | [INFO] [stdout] 109 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step7/src/parse.rs:117:21 [INFO] [stdout] | [INFO] [stdout] 117 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step7/src/parse.rs:124:21 [INFO] [stdout] | [INFO] [stdout] 124 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step7/src/parse.rs:134:21 [INFO] [stdout] | [INFO] [stdout] 134 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step7/src/parse.rs:149:21 [INFO] [stdout] | [INFO] [stdout] 149 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> stepA/src/parse.rs:20:21 [INFO] [stdout] | [INFO] [stdout] 20 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see 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 `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> stepA/src/parse.rs:28:21 [INFO] [stdout] | [INFO] [stdout] 28 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> stepA/src/parse.rs:34:21 [INFO] [stdout] | [INFO] [stdout] 34 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> stepA/src/parse.rs:40:21 [INFO] [stdout] | [INFO] [stdout] 40 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> stepA/src/parse.rs:46:21 [INFO] [stdout] | [INFO] [stdout] 46 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> stepA/src/parse.rs:52:21 [INFO] [stdout] | [INFO] [stdout] 52 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> stepA/src/parse.rs:59:21 [INFO] [stdout] | [INFO] [stdout] 59 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> stepA/src/parse.rs:66:21 [INFO] [stdout] | [INFO] [stdout] 66 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> stepA/src/parse.rs:73:21 [INFO] [stdout] | [INFO] [stdout] 73 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> stepA/src/parse.rs:80:21 [INFO] [stdout] | [INFO] [stdout] 80 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> stepA/src/parse.rs:87:21 [INFO] [stdout] | [INFO] [stdout] 87 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> stepA/src/parse.rs:95:21 [INFO] [stdout] | [INFO] [stdout] 95 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> stepA/src/parse.rs:102:21 [INFO] [stdout] | [INFO] [stdout] 102 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> stepA/src/parse.rs:109:21 [INFO] [stdout] | [INFO] [stdout] 109 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> stepA/src/parse.rs:117:21 [INFO] [stdout] | [INFO] [stdout] 117 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> stepA/src/parse.rs:124:21 [INFO] [stdout] | [INFO] [stdout] 124 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> stepA/src/parse.rs:134:21 [INFO] [stdout] | [INFO] [stdout] 134 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> stepA/src/parse.rs:149:21 [INFO] [stdout] | [INFO] [stdout] 149 | #[derive(Debug, FromPest)] [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 `FromPest` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused doc comment [INFO] [stdout] --> stepA/src/stdfn_part3.rs:153:9 [INFO] [stdout] | [INFO] [stdout] 153 | /// Convert user-defined function into a macro [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ rustdoc does not generate documentation for macro invocations [INFO] [stdout] | [INFO] [stdout] = help: to document an item produced by a macro, the macro must produce the documentation as part of its expansion [INFO] [stdout] = note: `#[warn(unused_doc_comments)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused doc comment [INFO] [stdout] --> stepA/src/stdfn_part3.rs:166:9 [INFO] [stdout] | [INFO] [stdout] 166 | /// Convert user-defined macro into a function [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ rustdoc does not generate documentation for macro invocations [INFO] [stdout] | [INFO] [stdout] = help: to document an item produced by a macro, the macro must produce the documentation as part of its expansion [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the feature `convert_id` has been stable since 1.33.0 and no longer requires an attribute to enable [INFO] [stdout] --> step7/src/lib.rs:2:12 [INFO] [stdout] | [INFO] [stdout] 2 | #![feature(convert_id)] [INFO] [stdout] | ^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(stable_features)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the feature `str_escape` has been stable since 1.34.0 and no longer requires an attribute to enable [INFO] [stdout] --> step7/src/lib.rs:3:12 [INFO] [stdout] | [INFO] [stdout] 3 | #![feature(str_escape)] [INFO] [stdout] | ^^^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: trait objects without an explicit `dyn` are deprecated [INFO] [stdout] --> step7/src/lib.rs:114:16 [INFO] [stdout] | [INFO] [stdout] 114 | type Func = Rc>) -> Result>; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this is accepted in the current edition (Rust 2018) but is a hard error in Rust 2021! [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: `#[warn(bare_trait_objects)]` on by default [INFO] [stdout] help: if this is a dyn-compatible trait, use `dyn` [INFO] [stdout] | [INFO] [stdout] 114 | type Func = Rc>) -> Result>; [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the feature `bind_by_move_pattern_guards` has been stable since 1.39.0 and no longer requires an attribute to enable [INFO] [stdout] --> stepA/src/lib.rs:4:12 [INFO] [stdout] | [INFO] [stdout] 4 | #![feature(bind_by_move_pattern_guards)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(stable_features)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the feature `convert_id` has been stable since 1.33.0 and no longer requires an attribute to enable [INFO] [stdout] --> stepA/src/lib.rs:2:12 [INFO] [stdout] | [INFO] [stdout] 2 | #![feature(convert_id)] [INFO] [stdout] | ^^^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the feature `str_escape` has been stable since 1.34.0 and no longer requires an attribute to enable [INFO] [stdout] --> stepA/src/lib.rs:3:12 [INFO] [stdout] | [INFO] [stdout] 3 | #![feature(str_escape)] [INFO] [stdout] | ^^^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the feature `try_from` has been stable since 1.34.0 and no longer requires an attribute to enable [INFO] [stdout] --> stepA/src/lib.rs:6:12 [INFO] [stdout] | [INFO] [stdout] 6 | #![feature(try_from)] [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: trait objects without an explicit `dyn` are deprecated [INFO] [stdout] --> stepA/src/lib.rs:163:16 [INFO] [stdout] | [INFO] [stdout] 163 | type Func = Rc>) -> Result>; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this is accepted in the current edition (Rust 2018) but is a hard error in Rust 2021! [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: `#[warn(bare_trait_objects)]` on by default [INFO] [stdout] help: if this is a dyn-compatible trait, use `dyn` [INFO] [stdout] | [INFO] [stdout] 163 | type Func = Rc>) -> Result>; [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] error: could not compile `malvi_step3b` (lib); 20 warnings emitted [INFO] [stderr] [INFO] [stderr] Caused by: [INFO] [stderr] No space left on device (os error 28) [INFO] [stderr] [INFO] [stderr] Caused by: [INFO] [stderr] failed to parse process output: `/opt/rustwide/rustup-home/toolchains/121a90d34197f711021eeb158e7f4184b8be8ceb/bin/rustc --crate-name malvi_step3b --edition=2018 step3b/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata -C embed-bitcode=no -C debuginfo=2 --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values())' -C metadata=d0fe9c1f43e6a985 -C extra-filename=-dfe2097dd6b53758 --out-dir /opt/rustwide/target/debug/deps -L dependency=/opt/rustwide/target/debug/deps --extern failure=/opt/rustwide/target/debug/deps/libfailure-0d45538a71461cea.rmeta --extern pest=/opt/rustwide/target/debug/deps/libpest-c9280300597725bd.rmeta --extern pest_deconstruct=/opt/rustwide/target/debug/deps/libpest_deconstruct-3c16b5cc57598f2b.rmeta --extern pest_derive=/opt/rustwide/target/debug/deps/libpest_derive-e465a8f541a54872.so --extern slab_typesafe=/opt/rustwide/target/debug/deps/libslab_typesafe-9ceb32614ebf3c49.rmeta --cap-lints=forbid -L native=/opt/rustwide/target/debug/build/backtrace-sys-1b502a9022900bbf/out` (exit status: 0) [INFO] [stderr] warning: build failed, waiting for other jobs to finish... [INFO] [stderr] error: could not compile `malvi_step3d` (lib); 1 warning emitted [INFO] [stderr] [INFO] [stderr] Caused by: [INFO] [stderr] No space left on device (os error 28) [INFO] [stderr] [INFO] [stderr] Caused by: [INFO] [stderr] failed to parse process output: `/opt/rustwide/rustup-home/toolchains/121a90d34197f711021eeb158e7f4184b8be8ceb/bin/rustc --crate-name malvi_step3d --edition=2018 step3d/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata -C embed-bitcode=no -C debuginfo=2 --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values())' -C metadata=fcf4b04375914ad9 -C extra-filename=-ff32b0d339d3e3ec --out-dir /opt/rustwide/target/debug/deps -L dependency=/opt/rustwide/target/debug/deps --extern failure=/opt/rustwide/target/debug/deps/libfailure-0d45538a71461cea.rmeta --extern im_rc=/opt/rustwide/target/debug/deps/libim_rc-5553bfd850b1d7e8.rmeta --extern itertools=/opt/rustwide/target/debug/deps/libitertools-510439fa19abab33.rmeta --extern pest=/opt/rustwide/target/debug/deps/libpest-c9280300597725bd.rmeta --extern pest_deconstruct=/opt/rustwide/target/debug/deps/libpest_deconstruct-3c16b5cc57598f2b.rmeta --extern pest_derive=/opt/rustwide/target/debug/deps/libpest_derive-e465a8f541a54872.so --extern slab_typesafe=/opt/rustwide/target/debug/deps/libslab_typesafe-9ceb32614ebf3c49.rmeta --cap-lints=forbid -L native=/opt/rustwide/target/debug/build/backtrace-sys-1b502a9022900bbf/out` (exit status: 0) [INFO] [stderr] error: could not compile `malvi_step9` (lib); 1 warning emitted [INFO] [stderr] [INFO] [stderr] Caused by: [INFO] [stderr] No space left on device (os error 28) [INFO] [stderr] [INFO] [stderr] Caused by: [INFO] [stderr] failed to parse process output: `/opt/rustwide/rustup-home/toolchains/121a90d34197f711021eeb158e7f4184b8be8ceb/bin/rustc --crate-name malvi_step9 --edition=2018 step9/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata -C embed-bitcode=no -C debuginfo=2 --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values())' -C metadata=e7cc2bdb9065972d -C extra-filename=-1fddbfffc6dff2ba --out-dir /opt/rustwide/target/debug/deps -L dependency=/opt/rustwide/target/debug/deps --extern failure=/opt/rustwide/target/debug/deps/libfailure-0d45538a71461cea.rmeta --extern im_rc=/opt/rustwide/target/debug/deps/libim_rc-5553bfd850b1d7e8.rmeta --extern itertools=/opt/rustwide/target/debug/deps/libitertools-510439fa19abab33.rmeta --extern pest=/opt/rustwide/target/debug/deps/libpest-c9280300597725bd.rmeta --extern pest_deconstruct=/opt/rustwide/target/debug/deps/libpest_deconstruct-3c16b5cc57598f2b.rmeta --extern pest_derive=/opt/rustwide/target/debug/deps/libpest_derive-e465a8f541a54872.so --extern slab_typesafe=/opt/rustwide/target/debug/deps/libslab_typesafe-9ceb32614ebf3c49.rmeta --extern unescape=/opt/rustwide/target/debug/deps/libunescape-97bc6c4e24d31634.rmeta --cap-lints=forbid -L native=/opt/rustwide/target/debug/build/backtrace-sys-1b502a9022900bbf/out` (exit status: 0) [INFO] [stderr] error: could not compile `malvi_step3c` (lib); 11 warnings emitted [INFO] [stderr] [INFO] [stderr] Caused by: [INFO] [stderr] No space left on device (os error 28) [INFO] [stderr] [INFO] [stderr] Caused by: [INFO] [stderr] failed to parse process output: `/opt/rustwide/rustup-home/toolchains/121a90d34197f711021eeb158e7f4184b8be8ceb/bin/rustc --crate-name malvi_step3c --edition=2018 step3c/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata -C embed-bitcode=no -C debuginfo=2 --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values())' -C metadata=8508da36de1bad05 -C extra-filename=-f2c0dd3f727ed32c --out-dir /opt/rustwide/target/debug/deps -L dependency=/opt/rustwide/target/debug/deps --extern failure=/opt/rustwide/target/debug/deps/libfailure-0d45538a71461cea.rmeta --extern pest=/opt/rustwide/target/debug/deps/libpest-c9280300597725bd.rmeta --extern pest_deconstruct=/opt/rustwide/target/debug/deps/libpest_deconstruct-3c16b5cc57598f2b.rmeta --extern pest_derive=/opt/rustwide/target/debug/deps/libpest_derive-e465a8f541a54872.so --extern slab_typesafe=/opt/rustwide/target/debug/deps/libslab_typesafe-9ceb32614ebf3c49.rmeta --cap-lints=forbid -L native=/opt/rustwide/target/debug/build/backtrace-sys-1b502a9022900bbf/out` (exit status: 0) [INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item [INFO] [stdout] --> step4/src/parse.rs:20:21 [INFO] [stdout] | [INFO] [stdout] 20 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_Int` [INFO] [stdout] 21 | #[pest(rule = "Rule::int")] [INFO] [stdout] 22 | pub struct Int<'i> { [INFO] [stdout] | --- `Int` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> step4/src/parse.rs:28:21 [INFO] [stdout] | [INFO] [stdout] 28 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_Symbol` [INFO] [stdout] 29 | #[pest(rule = "Rule::symbol")] [INFO] [stdout] 30 | pub struct Symbol<'i> { [INFO] [stdout] | ------ `Symbol` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> step4/src/parse.rs:34:21 [INFO] [stdout] | [INFO] [stdout] 34 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_Keyword` [INFO] [stdout] 35 | #[pest(rule = "Rule::kw")] [INFO] [stdout] 36 | pub struct Keyword<'i> { [INFO] [stdout] | ------- `Keyword` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> step4/src/parse.rs:40:21 [INFO] [stdout] | [INFO] [stdout] 40 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_Atom` [INFO] [stdout] 41 | #[pest(rule = "Rule::atom")] [INFO] [stdout] 42 | pub struct Atom<'i> { [INFO] [stdout] | ---- `Atom` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> step4/src/parse.rs:46:21 [INFO] [stdout] | [INFO] [stdout] 46 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_StrLit` [INFO] [stdout] 47 | #[pest(rule = "Rule::strlit")] [INFO] [stdout] 48 | pub struct StrLit<'i> { [INFO] [stdout] | ------ `StrLit` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> step4/src/parse.rs:52:21 [INFO] [stdout] | [INFO] [stdout] 52 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_Quote` [INFO] [stdout] 53 | #[pest(rule = "Rule::quote")] [INFO] [stdout] 54 | pub struct Quote<'i> { [INFO] [stdout] | ----- `Quote` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> step4/src/parse.rs:59:21 [INFO] [stdout] | [INFO] [stdout] 59 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_Quasiquote` [INFO] [stdout] 60 | #[pest(rule = "Rule::quasiquote")] [INFO] [stdout] 61 | pub struct Quasiquote<'i> { [INFO] [stdout] | ---------- `Quasiquote` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> step4/src/parse.rs:66:21 [INFO] [stdout] | [INFO] [stdout] 66 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_Unquote` [INFO] [stdout] 67 | #[pest(rule = "Rule::unquote")] [INFO] [stdout] 68 | pub struct Unquote<'i> { [INFO] [stdout] | ------- `Unquote` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> step4/src/parse.rs:73:21 [INFO] [stdout] | [INFO] [stdout] 73 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_Spliceunquote` [INFO] [stdout] 74 | #[pest(rule = "Rule::spliceunquote")] [INFO] [stdout] 75 | pub struct Spliceunquote<'i> { [INFO] [stdout] | ------------- `Spliceunquote` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> step4/src/parse.rs:80:21 [INFO] [stdout] | [INFO] [stdout] 80 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_Deref` [INFO] [stdout] 81 | #[pest(rule = "Rule::deref")] [INFO] [stdout] 82 | pub struct Deref<'i> { [INFO] [stdout] | ----- `Deref` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> step4/src/parse.rs:87:21 [INFO] [stdout] | [INFO] [stdout] 87 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_Withmeta` [INFO] [stdout] 88 | #[pest(rule = "Rule::withmeta")] [INFO] [stdout] 89 | pub struct Withmeta<'i> { [INFO] [stdout] | -------- `Withmeta` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> step4/src/parse.rs:95:21 [INFO] [stdout] | [INFO] [stdout] 95 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_Round` [INFO] [stdout] 96 | #[pest(rule = "Rule::round")] [INFO] [stdout] 97 | pub struct Round<'i> { [INFO] [stdout] | ----- `Round` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> step4/src/parse.rs:102:21 [INFO] [stdout] | [INFO] [stdout] 102 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_Square` [INFO] [stdout] 103 | #[pest(rule = "Rule::square")] [INFO] [stdout] 104 | pub struct Square<'i> { [INFO] [stdout] | ------ `Square` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> step4/src/parse.rs:109:21 [INFO] [stdout] | [INFO] [stdout] 109 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_CurlyItem` [INFO] [stdout] 110 | #[pest(rule = "Rule::curly_item")] [INFO] [stdout] 111 | pub struct CurlyItem<'i> { [INFO] [stdout] | --------- `CurlyItem` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> step4/src/parse.rs:117:21 [INFO] [stdout] | [INFO] [stdout] 117 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_Curly` [INFO] [stdout] 118 | #[pest(rule = "Rule::curly")] [INFO] [stdout] 119 | pub struct Curly<'i> { [INFO] [stdout] | ----- `Curly` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> step4/src/parse.rs:124:21 [INFO] [stdout] | [INFO] [stdout] 124 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_SimpleObj` [INFO] [stdout] 125 | #[pest(rule = "Rule::obj_simple")] [INFO] [stdout] 126 | pub enum SimpleObj<'i> { [INFO] [stdout] | --------- `SimpleObj` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> step4/src/parse.rs:134:21 [INFO] [stdout] | [INFO] [stdout] 134 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_Obj` [INFO] [stdout] 135 | #[pest(rule = "Rule::obj")] [INFO] [stdout] 136 | pub enum Obj<'i> { [INFO] [stdout] | --- `Obj` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> step4/src/parse.rs:149:21 [INFO] [stdout] | [INFO] [stdout] 149 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_MObj` [INFO] [stdout] ... [INFO] [stdout] 152 | pub struct MObj<'i> { [INFO] [stdout] | ---- `MObj` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `std::result::Result` that must be used [INFO] [stdout] --> step7/src/parse.rs:230:13 [INFO] [stdout] | [INFO] [stdout] 230 | write!(f, " "); [INFO] [stdout] | ^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] = note: `#[warn(unused_must_use)]` on by default [INFO] [stdout] = note: this warning originates in the macro `write` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `std::result::Result` that must be used [INFO] [stdout] --> step7/src/parse.rs:232:9 [INFO] [stdout] | [INFO] [stdout] 232 | write!(f, "{}", BoundAstRef(&*i, m, dm)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] = note: this warning originates in the macro `write` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `std::result::Result` that must be used [INFO] [stdout] --> step7/src/parse.rs:254:17 [INFO] [stdout] | [INFO] [stdout] 254 | write!(f, "("); [INFO] [stdout] | ^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] = note: this warning originates in the macro `write` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `std::result::Result` that must be used [INFO] [stdout] --> step7/src/parse.rs:259:17 [INFO] [stdout] | [INFO] [stdout] 259 | write!(f, "["); [INFO] [stdout] | ^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] = note: this warning originates in the macro `write` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `std::result::Result` that must be used [INFO] [stdout] --> step7/src/parse.rs:264:17 [INFO] [stdout] | [INFO] [stdout] 264 | write!(f, "{{"); [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] = note: this warning originates in the macro `write` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `std::result::Result` that must be used [INFO] [stdout] --> step7/src/parse.rs:268:25 [INFO] [stdout] | [INFO] [stdout] 268 | write!(f, ", "); [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] = note: this warning originates in the macro `write` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `std::result::Result` that must be used [INFO] [stdout] --> step7/src/parse.rs:270:21 [INFO] [stdout] | [INFO] [stdout] 270 | / write!( [INFO] [stdout] 271 | | f, [INFO] [stdout] 272 | | "{} {}", [INFO] [stdout] 273 | | BoundAstRef(&Ast::Simple(k.clone()), m, dm), [INFO] [stdout] 274 | | BoundAstRef(v, m, dm), [INFO] [stdout] 275 | | ); [INFO] [stdout] | |_____________________^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] = note: this warning originates in the macro `write` (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] --> step7/src/parse.rs:20:21 [INFO] [stdout] | [INFO] [stdout] 20 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_Int` [INFO] [stdout] 21 | #[pest(rule = "Rule::int")] [INFO] [stdout] 22 | pub struct Int<'i> { [INFO] [stdout] | --- `Int` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> step7/src/parse.rs:28:21 [INFO] [stdout] | [INFO] [stdout] 28 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_Symbol` [INFO] [stdout] 29 | #[pest(rule = "Rule::symbol")] [INFO] [stdout] 30 | pub struct Symbol<'i> { [INFO] [stdout] | ------ `Symbol` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> step7/src/parse.rs:34:21 [INFO] [stdout] | [INFO] [stdout] 34 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_Keyword` [INFO] [stdout] 35 | #[pest(rule = "Rule::kw")] [INFO] [stdout] 36 | pub struct Keyword<'i> { [INFO] [stdout] | ------- `Keyword` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> step7/src/parse.rs:40:21 [INFO] [stdout] | [INFO] [stdout] 40 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_Kwident` [INFO] [stdout] 41 | #[pest(rule = "Rule::kwident")] [INFO] [stdout] 42 | pub struct Kwident<'i> { [INFO] [stdout] | ------- `Kwident` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> step7/src/parse.rs:46:21 [INFO] [stdout] | [INFO] [stdout] 46 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_StrLit` [INFO] [stdout] 47 | #[pest(rule = "Rule::strlit")] [INFO] [stdout] 48 | pub struct StrLit<'i> { [INFO] [stdout] | ------ `StrLit` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> step7/src/parse.rs:52:21 [INFO] [stdout] | [INFO] [stdout] 52 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_Quote` [INFO] [stdout] 53 | #[pest(rule = "Rule::quote")] [INFO] [stdout] 54 | pub struct Quote<'i> { [INFO] [stdout] | ----- `Quote` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> step7/src/parse.rs:59:21 [INFO] [stdout] | [INFO] [stdout] 59 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_Quasiquote` [INFO] [stdout] 60 | #[pest(rule = "Rule::quasiquote")] [INFO] [stdout] 61 | pub struct Quasiquote<'i> { [INFO] [stdout] | ---------- `Quasiquote` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> step7/src/parse.rs:66:21 [INFO] [stdout] | [INFO] [stdout] 66 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_Unquote` [INFO] [stdout] 67 | #[pest(rule = "Rule::unquote")] [INFO] [stdout] 68 | pub struct Unquote<'i> { [INFO] [stdout] | ------- `Unquote` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> step7/src/parse.rs:73:21 [INFO] [stdout] | [INFO] [stdout] 73 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_Spliceunquote` [INFO] [stdout] 74 | #[pest(rule = "Rule::spliceunquote")] [INFO] [stdout] 75 | pub struct Spliceunquote<'i> { [INFO] [stdout] | ------------- `Spliceunquote` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> step7/src/parse.rs:80:21 [INFO] [stdout] | [INFO] [stdout] 80 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_Deref` [INFO] [stdout] 81 | #[pest(rule = "Rule::deref")] [INFO] [stdout] 82 | pub struct Deref<'i> { [INFO] [stdout] | ----- `Deref` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> step7/src/parse.rs:87:21 [INFO] [stdout] | [INFO] [stdout] 87 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_Withmeta` [INFO] [stdout] 88 | #[pest(rule = "Rule::withmeta")] [INFO] [stdout] 89 | pub struct Withmeta<'i> { [INFO] [stdout] | -------- `Withmeta` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> step7/src/parse.rs:95:21 [INFO] [stdout] | [INFO] [stdout] 95 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_Round` [INFO] [stdout] 96 | #[pest(rule = "Rule::round")] [INFO] [stdout] 97 | pub struct Round<'i> { [INFO] [stdout] | ----- `Round` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> step7/src/parse.rs:102:21 [INFO] [stdout] | [INFO] [stdout] 102 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_Square` [INFO] [stdout] 103 | #[pest(rule = "Rule::square")] [INFO] [stdout] 104 | pub struct Square<'i> { [INFO] [stdout] | ------ `Square` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> step7/src/parse.rs:109:21 [INFO] [stdout] | [INFO] [stdout] 109 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_CurlyItem` [INFO] [stdout] 110 | #[pest(rule = "Rule::curly_item")] [INFO] [stdout] 111 | pub struct CurlyItem<'i> { [INFO] [stdout] | --------- `CurlyItem` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> step7/src/parse.rs:117:21 [INFO] [stdout] | [INFO] [stdout] 117 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_Curly` [INFO] [stdout] 118 | #[pest(rule = "Rule::curly")] [INFO] [stdout] 119 | pub struct Curly<'i> { [INFO] [stdout] | ----- `Curly` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> step7/src/parse.rs:124:21 [INFO] [stdout] | [INFO] [stdout] 124 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_SimpleObj` [INFO] [stdout] 125 | #[pest(rule = "Rule::obj_simple")] [INFO] [stdout] 126 | pub enum SimpleObj<'i> { [INFO] [stdout] | --------- `SimpleObj` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> step7/src/parse.rs:134:21 [INFO] [stdout] | [INFO] [stdout] 134 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_Obj` [INFO] [stdout] 135 | #[pest(rule = "Rule::obj")] [INFO] [stdout] 136 | pub enum Obj<'i> { [INFO] [stdout] | --- `Obj` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> step7/src/parse.rs:149:21 [INFO] [stdout] | [INFO] [stdout] 149 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_MObj` [INFO] [stdout] ... [INFO] [stdout] 152 | pub struct MObj<'i> { [INFO] [stdout] | ---- `MObj` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `std::result::Result` that must be used [INFO] [stdout] --> step7/src/stdfn_part2.rs:93:21 [INFO] [stdout] | [INFO] [stdout] 93 | write!(s, " "); [INFO] [stdout] | ^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] = note: this warning originates in the macro `write` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `std::result::Result` that must be used [INFO] [stdout] --> step7/src/stdfn_part2.rs:95:17 [INFO] [stdout] | [INFO] [stdout] 95 | write!(s, "{}", super::BoundAstRef(&*x, m, crate::DisplayMode::PrStr)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] = note: this warning originates in the macro `write` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `std::result::Result` that must be used [INFO] [stdout] --> step7/src/stdfn_part2.rs:105:17 [INFO] [stdout] | [INFO] [stdout] 105 | write!(s, "{}", super::BoundAstRef(&*x, m, crate::DisplayMode::Str)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] = note: this warning originates in the macro `write` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] error: could not compile `malvi_step8` (lib); 11 warnings emitted [INFO] [stderr] [INFO] [stderr] Caused by: [INFO] [stderr] No space left on device (os error 28) [INFO] [stderr] [INFO] [stderr] Caused by: [INFO] [stderr] failed to parse process output: `/opt/rustwide/rustup-home/toolchains/121a90d34197f711021eeb158e7f4184b8be8ceb/bin/rustc --crate-name malvi_step8 --edition=2018 step8/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata -C embed-bitcode=no -C debuginfo=2 --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values())' -C metadata=72bf434d5a6325e0 -C extra-filename=-164b0222f9649b92 --out-dir /opt/rustwide/target/debug/deps -L dependency=/opt/rustwide/target/debug/deps --extern failure=/opt/rustwide/target/debug/deps/libfailure-0d45538a71461cea.rmeta --extern im_rc=/opt/rustwide/target/debug/deps/libim_rc-5553bfd850b1d7e8.rmeta --extern itertools=/opt/rustwide/target/debug/deps/libitertools-510439fa19abab33.rmeta --extern pest=/opt/rustwide/target/debug/deps/libpest-c9280300597725bd.rmeta --extern pest_deconstruct=/opt/rustwide/target/debug/deps/libpest_deconstruct-3c16b5cc57598f2b.rmeta --extern pest_derive=/opt/rustwide/target/debug/deps/libpest_derive-e465a8f541a54872.so --extern slab_typesafe=/opt/rustwide/target/debug/deps/libslab_typesafe-9ceb32614ebf3c49.rmeta --extern unescape=/opt/rustwide/target/debug/deps/libunescape-97bc6c4e24d31634.rmeta --cap-lints=forbid -L native=/opt/rustwide/target/debug/build/backtrace-sys-1b502a9022900bbf/out` (exit status: 0) [INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item [INFO] [stdout] --> stepA/src/parse.rs:20:21 [INFO] [stdout] | [INFO] [stdout] 20 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_Int` [INFO] [stdout] 21 | #[pest(rule = "Rule::int")] [INFO] [stdout] 22 | pub struct Int<'i> { [INFO] [stdout] | --- `Int` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> stepA/src/parse.rs:28:21 [INFO] [stdout] | [INFO] [stdout] 28 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_Symbol` [INFO] [stdout] 29 | #[pest(rule = "Rule::symbol")] [INFO] [stdout] 30 | pub struct Symbol<'i> { [INFO] [stdout] | ------ `Symbol` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> stepA/src/parse.rs:34:21 [INFO] [stdout] | [INFO] [stdout] 34 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_Keyword` [INFO] [stdout] 35 | #[pest(rule = "Rule::kw")] [INFO] [stdout] 36 | pub struct Keyword<'i> { [INFO] [stdout] | ------- `Keyword` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> stepA/src/parse.rs:40:21 [INFO] [stdout] | [INFO] [stdout] 40 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_Kwident` [INFO] [stdout] 41 | #[pest(rule = "Rule::kwident")] [INFO] [stdout] 42 | pub struct Kwident<'i> { [INFO] [stdout] | ------- `Kwident` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> stepA/src/parse.rs:46:21 [INFO] [stdout] | [INFO] [stdout] 46 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_StrLit` [INFO] [stdout] 47 | #[pest(rule = "Rule::strlit")] [INFO] [stdout] 48 | pub struct StrLit<'i> { [INFO] [stdout] | ------ `StrLit` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> stepA/src/parse.rs:52:21 [INFO] [stdout] | [INFO] [stdout] 52 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_Quote` [INFO] [stdout] 53 | #[pest(rule = "Rule::quote")] [INFO] [stdout] 54 | pub struct Quote<'i> { [INFO] [stdout] | ----- `Quote` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> stepA/src/parse.rs:59:21 [INFO] [stdout] | [INFO] [stdout] 59 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_Quasiquote` [INFO] [stdout] 60 | #[pest(rule = "Rule::quasiquote")] [INFO] [stdout] 61 | pub struct Quasiquote<'i> { [INFO] [stdout] | ---------- `Quasiquote` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> stepA/src/parse.rs:66:21 [INFO] [stdout] | [INFO] [stdout] 66 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_Unquote` [INFO] [stdout] 67 | #[pest(rule = "Rule::unquote")] [INFO] [stdout] 68 | pub struct Unquote<'i> { [INFO] [stdout] | ------- `Unquote` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> stepA/src/parse.rs:73:21 [INFO] [stdout] | [INFO] [stdout] 73 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_Spliceunquote` [INFO] [stdout] 74 | #[pest(rule = "Rule::spliceunquote")] [INFO] [stdout] 75 | pub struct Spliceunquote<'i> { [INFO] [stdout] | ------------- `Spliceunquote` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> stepA/src/parse.rs:80:21 [INFO] [stdout] | [INFO] [stdout] 80 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_Deref` [INFO] [stdout] 81 | #[pest(rule = "Rule::deref")] [INFO] [stdout] 82 | pub struct Deref<'i> { [INFO] [stdout] | ----- `Deref` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> stepA/src/parse.rs:87:21 [INFO] [stdout] | [INFO] [stdout] 87 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_Withmeta` [INFO] [stdout] 88 | #[pest(rule = "Rule::withmeta")] [INFO] [stdout] 89 | pub struct Withmeta<'i> { [INFO] [stdout] | -------- `Withmeta` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> stepA/src/parse.rs:95:21 [INFO] [stdout] | [INFO] [stdout] 95 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_Round` [INFO] [stdout] 96 | #[pest(rule = "Rule::round")] [INFO] [stdout] 97 | pub struct Round<'i> { [INFO] [stdout] | ----- `Round` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> stepA/src/parse.rs:102:21 [INFO] [stdout] | [INFO] [stdout] 102 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_Square` [INFO] [stdout] 103 | #[pest(rule = "Rule::square")] [INFO] [stdout] 104 | pub struct Square<'i> { [INFO] [stdout] | ------ `Square` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> stepA/src/parse.rs:109:21 [INFO] [stdout] | [INFO] [stdout] 109 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_CurlyItem` [INFO] [stdout] 110 | #[pest(rule = "Rule::curly_item")] [INFO] [stdout] 111 | pub struct CurlyItem<'i> { [INFO] [stdout] | --------- `CurlyItem` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> stepA/src/parse.rs:117:21 [INFO] [stdout] | [INFO] [stdout] 117 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_Curly` [INFO] [stdout] 118 | #[pest(rule = "Rule::curly")] [INFO] [stdout] 119 | pub struct Curly<'i> { [INFO] [stdout] | ----- `Curly` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> stepA/src/parse.rs:124:21 [INFO] [stdout] | [INFO] [stdout] 124 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_SimpleObj` [INFO] [stdout] 125 | #[pest(rule = "Rule::obj_simple")] [INFO] [stdout] 126 | pub enum SimpleObj<'i> { [INFO] [stdout] | --------- `SimpleObj` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> stepA/src/parse.rs:134:21 [INFO] [stdout] | [INFO] [stdout] 134 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_Obj` [INFO] [stdout] 135 | #[pest(rule = "Rule::obj")] [INFO] [stdout] 136 | pub enum Obj<'i> { [INFO] [stdout] | --- `Obj` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (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] --> stepA/src/parse.rs:149:21 [INFO] [stdout] | [INFO] [stdout] 149 | #[derive(Debug, FromPest)] [INFO] [stdout] | ^------- [INFO] [stdout] | | [INFO] [stdout] | `FromPest` is not local [INFO] [stdout] | move the `impl` block outside of this constant `__IMPL_FromPest_FOR_MObj` [INFO] [stdout] ... [INFO] [stdout] 152 | pub struct MObj<'i> { [INFO] [stdout] | ---- `MObj` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPest` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPest` may come from an old version of the `derive` crate, try updating your dependency with `cargo update -p 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 `FromPest` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] running `Command { std: "docker" "inspect" "6ec94b8984aa6f14ca943d5625139f86cecc033439821138f66a10d0e8c743d3", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "6ec94b8984aa6f14ca943d5625139f86cecc033439821138f66a10d0e8c743d3", kill_on_drop: false }` [INFO] [stdout] 6ec94b8984aa6f14ca943d5625139f86cecc033439821138f66a10d0e8c743d3