[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 master#092a284ba0421695f2032c947765429fd7095796 for pr-139763 [INFO] running `Command { std: "git" "clone" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fvi%2Fmal-rust-vi" "/workspace/builds/worker-4-tc1/source", kill_on_drop: false }` [INFO] [stderr] Cloning into '/workspace/builds/worker-4-tc1/source'... [INFO] [stderr] done. [INFO] validating manifest of git repo https://github.com/vi/mal-rust-vi on toolchain 092a284ba0421695f2032c947765429fd7095796 [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+092a284ba0421695f2032c947765429fd7095796" "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-4-tc1/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" "+092a284ba0421695f2032c947765429fd7095796" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Blocking waiting for file lock on package cache [INFO] [stderr] Updating crates.io index [INFO] [stderr] Downloading crates ... [INFO] [stderr] Downloaded pest_meta v2.0.3 [INFO] [stderr] Downloaded im-rc v12.2.0 [INFO] [stderr] Downloaded pest v2.0.1 [INFO] [stderr] Downloaded syn v0.15.11 [INFO] [stderr] Downloaded pest-deconstruct v0.2.0 [INFO] [stderr] Downloaded pest-deconstruct-derive v0.2.0 [INFO] [stderr] Downloaded slab_typesafe v0.1.2 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc1/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" "+092a284ba0421695f2032c947765429fd7095796" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] 7c28238372c3981aa9489862754c843230300c6abbc8e8828931d9f52b088724 [INFO] running `Command { std: "docker" "start" "-a" "7c28238372c3981aa9489862754c843230300c6abbc8e8828931d9f52b088724", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "7c28238372c3981aa9489862754c843230300c6abbc8e8828931d9f52b088724", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "7c28238372c3981aa9489862754c843230300c6abbc8e8828931d9f52b088724", kill_on_drop: false }` [INFO] [stdout] 7c28238372c3981aa9489862754c843230300c6abbc8e8828931d9f52b088724 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc1/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" "+092a284ba0421695f2032c947765429fd7095796" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] 47aacd7aa43db044f71a09a9b4d7af64d2947d0000f1f621272aefcecc7c5331 [INFO] running `Command { std: "docker" "start" "-a" "47aacd7aa43db044f71a09a9b4d7af64d2947d0000f1f621272aefcecc7c5331", kill_on_drop: false }` [INFO] [stderr] Compiling proc-macro2 v0.4.20 [INFO] [stderr] Compiling unicode-xid v0.1.0 [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 rustc-demangle v0.1.9 [INFO] [stderr] Compiling cfg-if v0.1.5 [INFO] [stderr] Compiling ucd-trie v0.1.1 [INFO] [stderr] Compiling either v1.5.0 [INFO] [stderr] Compiling pest v2.0.1 [INFO] [stderr] Compiling maplit v1.0.1 [INFO] [stderr] Compiling itertools v0.7.8 [INFO] [stderr] Checking slab v0.4.1 [INFO] [stderr] Compiling semver-parser v0.7.0 [INFO] [stderr] Compiling typenum v1.10.0 [INFO] [stderr] Checking slab_typesafe v0.1.2 [INFO] [stderr] Compiling quote v0.6.8 [INFO] [stderr] Compiling semver v0.9.0 [INFO] [stderr] Compiling syn v0.14.9 [INFO] [stderr] Compiling syn v0.15.11 [INFO] [stderr] Compiling rustc_version v0.2.3 [INFO] [stderr] Compiling backtrace-sys v0.1.24 [INFO] [stderr] Compiling im-rc v12.2.0 [INFO] [stderr] Checking unescape v0.1.0 [INFO] [stderr] Compiling pest_meta v2.0.3 [INFO] [stderr] Checking malvi_step0 v0.1.0 (/opt/rustwide/workdir/step0) [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 failure v0.1.2 [INFO] [stderr] Compiling pest_derive v2.0.1 [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_final v0.1.0 (/opt/rustwide/workdir/final) [INFO] [stderr] Checking malvi_step9 v0.1.0 (/opt/rustwide/workdir/step9) [INFO] [stderr] Checking malvi_step3 v0.1.0 (/opt/rustwide/workdir/step3) [INFO] [stderr] Checking malvi_step3b v0.1.0 (/opt/rustwide/workdir/step3b) [INFO] [stderr] Checking malvi_step3c v0.1.0 (/opt/rustwide/workdir/step3c) [INFO] [stderr] Checking malvi_step2 v0.1.0 (/opt/rustwide/workdir/step2) [INFO] [stderr] Checking malvi_step7 v0.1.0 (/opt/rustwide/workdir/step7) [INFO] [stderr] Checking malvi_step6 v0.1.0 (/opt/rustwide/workdir/step6) [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: 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] --> 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] --> 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: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step3c/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] --> step3c/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] --> step3c/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] --> step3c/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] --> step3c/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] --> step3c/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: the feature `chunks_exact` has been stable since 1.31.0 and no longer requires an attribute to enable [INFO] [stdout] --> step3c/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] --> step3c/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] --> step3c/src/lib.rs:69:16 [INFO] [stdout] | [INFO] [stdout] 69 | 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] 69 | 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] --> 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] --> step9/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] --> step9/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] --> step9/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] --> step9/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] --> step9/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] --> step9/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] --> step9/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] --> step9/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] --> step9/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] --> step9/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] --> step9/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] --> step9/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] --> step9/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] --> step9/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] --> step9/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] --> step9/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] --> step9/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] --> step9/src/stdfn_part3.rs:145:9 [INFO] [stdout] | [INFO] [stdout] 145 | /// 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] --> step9/src/stdfn_part3.rs:158:9 [INFO] [stdout] | [INFO] [stdout] 158 | /// 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: 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: 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: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step3/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] --> step3/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] --> step3/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] --> step3/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] --> step3/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] --> step3/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] --> step3/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] --> step3/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] --> step3/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] --> step3/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] --> step3/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] --> step2/src/parse.rs:14:21 [INFO] [stdout] | [INFO] [stdout] 14 | #[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] --> step2/src/parse.rs:22:21 [INFO] [stdout] | [INFO] [stdout] 22 | #[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] --> step3/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] --> step3/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] --> step3/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] --> step3/src/parse.rs:113:21 [INFO] [stdout] | [INFO] [stdout] 113 | #[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] --> step2/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] --> step2/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] --> step2/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] --> step2/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] --> step2/src/parse.rs:53:21 [INFO] [stdout] | [INFO] [stdout] 53 | #[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] --> step2/src/parse.rs:60:21 [INFO] [stdout] | [INFO] [stdout] 60 | #[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] --> step2/src/parse.rs:67:21 [INFO] [stdout] | [INFO] [stdout] 67 | #[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] --> step2/src/parse.rs:74:21 [INFO] [stdout] | [INFO] [stdout] 74 | #[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] --> step2/src/parse.rs:81:21 [INFO] [stdout] | [INFO] [stdout] 81 | #[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] --> step2/src/parse.rs:89:21 [INFO] [stdout] | [INFO] [stdout] 89 | #[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] --> step2/src/parse.rs:96:21 [INFO] [stdout] | [INFO] [stdout] 96 | #[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] --> step2/src/parse.rs:103:21 [INFO] [stdout] | [INFO] [stdout] 103 | #[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] --> step2/src/parse.rs:110:21 [INFO] [stdout] | [INFO] [stdout] 110 | #[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: trait objects without an explicit `dyn` are deprecated [INFO] [stdout] --> step2/src/lib.rs:65:17 [INFO] [stdout] | [INFO] [stdout] 65 | type Func = Box 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] 65 | type Func = Box Result>; [INFO] [stdout] | +++ [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] --> step3/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 `bind_by_move_pattern_guards` has been stable since 1.39.0 and no longer requires an attribute to enable [INFO] [stdout] --> step9/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: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> final/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] --> final/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] --> final/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: the feature `convert_id` has been stable since 1.33.0 and no longer requires an attribute to enable [INFO] [stdout] --> step3/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] --> step3/src/lib.rs:69:16 [INFO] [stdout] | [INFO] [stdout] 69 | 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] 69 | type Func = Rc]) -> Result>; [INFO] [stdout] | +++ [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] --> step9/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] --> step9/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] --> step9/src/lib.rs:123:16 [INFO] [stdout] | [INFO] [stdout] 123 | 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] 123 | type Func = Rc>) -> Result>; [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> final/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] --> final/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] --> final/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] --> final/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] --> final/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] --> final/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] --> final/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] --> final/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] --> final/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] --> final/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] --> final/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] --> final/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] --> final/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] --> final/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] --> final/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] --> final/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] --> final/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 `bind_by_move_pattern_guards` has been stable since 1.39.0 and no longer requires an attribute to enable [INFO] [stdout] --> final/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] --> final/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] --> final/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] --> final/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] --> final/src/lib.rs:170:16 [INFO] [stdout] | [INFO] [stdout] 170 | 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] 170 | type Func = Rc>) -> Result>; [INFO] [stdout] | +++ [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] --> step2/src/parse.rs:14:21 [INFO] [stdout] | [INFO] [stdout] 14 | #[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] 15 | #[pest(rule = "Rule::int")] [INFO] [stdout] 16 | 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] --> step2/src/parse.rs:22:21 [INFO] [stdout] | [INFO] [stdout] 22 | #[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] 23 | #[pest(rule = "Rule::symbol")] [INFO] [stdout] 24 | 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] --> step2/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_Keyword` [INFO] [stdout] 29 | #[pest(rule = "Rule::kw")] [INFO] [stdout] 30 | 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] --> step2/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_Atom` [INFO] [stdout] 35 | #[pest(rule = "Rule::atom")] [INFO] [stdout] 36 | 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] --> step2/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_StrLit` [INFO] [stdout] 41 | #[pest(rule = "Rule::strlit")] [INFO] [stdout] 42 | 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] --> step2/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_Quote` [INFO] [stdout] 47 | #[pest(rule = "Rule::quote")] [INFO] [stdout] 48 | 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] --> step2/src/parse.rs:53:21 [INFO] [stdout] | [INFO] [stdout] 53 | #[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] 54 | #[pest(rule = "Rule::quasiquote")] [INFO] [stdout] 55 | 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] --> step2/src/parse.rs:60:21 [INFO] [stdout] | [INFO] [stdout] 60 | #[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] 61 | #[pest(rule = "Rule::unquote")] [INFO] [stdout] 62 | 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] --> step2/src/parse.rs:67:21 [INFO] [stdout] | [INFO] [stdout] 67 | #[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] 68 | #[pest(rule = "Rule::spliceunquote")] [INFO] [stdout] 69 | 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] --> step2/src/parse.rs:74:21 [INFO] [stdout] | [INFO] [stdout] 74 | #[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] 75 | #[pest(rule = "Rule::deref")] [INFO] [stdout] 76 | 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] --> step2/src/parse.rs:81:21 [INFO] [stdout] | [INFO] [stdout] 81 | #[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] 82 | #[pest(rule = "Rule::withmeta")] [INFO] [stdout] 83 | 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] --> step2/src/parse.rs:89:21 [INFO] [stdout] | [INFO] [stdout] 89 | #[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] 90 | #[pest(rule = "Rule::round")] [INFO] [stdout] 91 | 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] --> step2/src/parse.rs:96:21 [INFO] [stdout] | [INFO] [stdout] 96 | #[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] 97 | #[pest(rule = "Rule::square")] [INFO] [stdout] 98 | 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] --> step2/src/parse.rs:103:21 [INFO] [stdout] | [INFO] [stdout] 103 | #[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] 104 | #[pest(rule = "Rule::curly")] [INFO] [stdout] 105 | 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] --> step2/src/parse.rs:110:21 [INFO] [stdout] | [INFO] [stdout] 110 | #[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] 111 | #[pest(rule = "Rule::obj")] [INFO] [stdout] 112 | 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: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step6/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] --> step6/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] --> step6/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] --> step6/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] --> step6/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] --> step6/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] --> step6/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] --> step6/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] --> step6/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] --> step6/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] --> step6/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] --> step6/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] --> step6/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] --> step6/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: non-local `impl` definition, `impl` blocks should be written at the same level as their item [INFO] [stdout] --> step3c/src/parse.rs:17:21 [INFO] [stdout] | [INFO] [stdout] 17 | #[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] 18 | #[pest(rule = "Rule::int")] [INFO] [stdout] 19 | 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: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step6/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: non-local `impl` definition, `impl` blocks should be written at the same level as their item [INFO] [stdout] --> step3c/src/parse.rs:25:21 [INFO] [stdout] | [INFO] [stdout] 25 | #[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] 26 | #[pest(rule = "Rule::symbol")] [INFO] [stdout] 27 | 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: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step6/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: non-local `impl` definition, `impl` blocks should be written at the same level as their item [INFO] [stdout] --> step3c/src/parse.rs:31:21 [INFO] [stdout] | [INFO] [stdout] 31 | #[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] 32 | #[pest(rule = "Rule::kw")] [INFO] [stdout] 33 | 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] --> step3c/src/parse.rs:37:21 [INFO] [stdout] | [INFO] [stdout] 37 | #[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] 38 | #[pest(rule = "Rule::atom")] [INFO] [stdout] 39 | 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] --> step3c/src/parse.rs:43:21 [INFO] [stdout] | [INFO] [stdout] 43 | #[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] 44 | #[pest(rule = "Rule::strlit")] [INFO] [stdout] 45 | 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] --> step3c/src/parse.rs:49:21 [INFO] [stdout] | [INFO] [stdout] 49 | #[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] 50 | #[pest(rule = "Rule::quote")] [INFO] [stdout] 51 | 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] --> step3c/src/parse.rs:56:21 [INFO] [stdout] | [INFO] [stdout] 56 | #[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] 57 | #[pest(rule = "Rule::quasiquote")] [INFO] [stdout] 58 | 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] --> step3c/src/parse.rs:63:21 [INFO] [stdout] | [INFO] [stdout] 63 | #[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] 64 | #[pest(rule = "Rule::unquote")] [INFO] [stdout] 65 | 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] --> step3c/src/parse.rs:70:21 [INFO] [stdout] | [INFO] [stdout] 70 | #[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] 71 | #[pest(rule = "Rule::spliceunquote")] [INFO] [stdout] 72 | 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] --> step3c/src/parse.rs:77:21 [INFO] [stdout] | [INFO] [stdout] 77 | #[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] 78 | #[pest(rule = "Rule::deref")] [INFO] [stdout] 79 | 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] --> step3c/src/parse.rs:84:21 [INFO] [stdout] | [INFO] [stdout] 84 | #[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] 85 | #[pest(rule = "Rule::withmeta")] [INFO] [stdout] 86 | 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] --> step3c/src/parse.rs:92:21 [INFO] [stdout] | [INFO] [stdout] 92 | #[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] 93 | #[pest(rule = "Rule::round")] [INFO] [stdout] 94 | 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] --> step3c/src/parse.rs:99:21 [INFO] [stdout] | [INFO] [stdout] 99 | #[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] 100 | #[pest(rule = "Rule::square")] [INFO] [stdout] 101 | 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] --> step3c/src/parse.rs:106:21 [INFO] [stdout] | [INFO] [stdout] 106 | #[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] 107 | #[pest(rule = "Rule::curly_item")] [INFO] [stdout] 108 | 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] --> step3c/src/parse.rs:114:21 [INFO] [stdout] | [INFO] [stdout] 114 | #[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] 115 | #[pest(rule = "Rule::curly")] [INFO] [stdout] 116 | 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] --> step3c/src/parse.rs:121:21 [INFO] [stdout] | [INFO] [stdout] 121 | #[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] 122 | #[pest(rule = "Rule::obj_simple")] [INFO] [stdout] 123 | 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] --> step3c/src/parse.rs:131:21 [INFO] [stdout] | [INFO] [stdout] 131 | #[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] 132 | #[pest(rule = "Rule::obj")] [INFO] [stdout] 133 | 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: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step6/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] --> step6/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] --> step6/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] --> step6/src/lib.rs:3:12 [INFO] [stdout] | [INFO] [stdout] 3 | #![feature(str_escape)] [INFO] [stdout] | ^^^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Checking malvi_step4 v0.1.0 (/opt/rustwide/workdir/step4) [INFO] [stdout] warning: trait objects without an explicit `dyn` are deprecated [INFO] [stdout] --> step6/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] [stderr] Checking malvi_step5 v0.1.0 (/opt/rustwide/workdir/step5) [INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item [INFO] [stdout] --> step3/src/parse.rs:17:21 [INFO] [stdout] | [INFO] [stdout] 17 | #[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] 18 | #[pest(rule = "Rule::int")] [INFO] [stdout] 19 | 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] --> step3/src/parse.rs:25:21 [INFO] [stdout] | [INFO] [stdout] 25 | #[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] 26 | #[pest(rule = "Rule::symbol")] [INFO] [stdout] 27 | 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] --> step3/src/parse.rs:31:21 [INFO] [stdout] | [INFO] [stdout] 31 | #[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] 32 | #[pest(rule = "Rule::kw")] [INFO] [stdout] 33 | 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] --> step3/src/parse.rs:37:21 [INFO] [stdout] | [INFO] [stdout] 37 | #[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] 38 | #[pest(rule = "Rule::atom")] [INFO] [stdout] 39 | 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] --> step3/src/parse.rs:43:21 [INFO] [stdout] | [INFO] [stdout] 43 | #[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] 44 | #[pest(rule = "Rule::strlit")] [INFO] [stdout] 45 | 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] --> step3/src/parse.rs:49:21 [INFO] [stdout] | [INFO] [stdout] 49 | #[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] 50 | #[pest(rule = "Rule::quote")] [INFO] [stdout] 51 | 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] --> step3/src/parse.rs:56:21 [INFO] [stdout] | [INFO] [stdout] 56 | #[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] 57 | #[pest(rule = "Rule::quasiquote")] [INFO] [stdout] 58 | 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] --> step3/src/parse.rs:63:21 [INFO] [stdout] | [INFO] [stdout] 63 | #[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] 64 | #[pest(rule = "Rule::unquote")] [INFO] [stdout] 65 | 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] --> step3/src/parse.rs:70:21 [INFO] [stdout] | [INFO] [stdout] 70 | #[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] 71 | #[pest(rule = "Rule::spliceunquote")] [INFO] [stdout] 72 | 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] --> step3/src/parse.rs:77:21 [INFO] [stdout] | [INFO] [stdout] 77 | #[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] 78 | #[pest(rule = "Rule::deref")] [INFO] [stdout] 79 | 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] --> step3/src/parse.rs:84:21 [INFO] [stdout] | [INFO] [stdout] 84 | #[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] 85 | #[pest(rule = "Rule::withmeta")] [INFO] [stdout] 86 | 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] --> step3/src/parse.rs:92:21 [INFO] [stdout] | [INFO] [stdout] 92 | #[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] 93 | #[pest(rule = "Rule::round")] [INFO] [stdout] 94 | 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] --> step3/src/parse.rs:99:21 [INFO] [stdout] | [INFO] [stdout] 99 | #[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] 100 | #[pest(rule = "Rule::square")] [INFO] [stdout] 101 | 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] --> step3/src/parse.rs:106:21 [INFO] [stdout] | [INFO] [stdout] 106 | #[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] 107 | #[pest(rule = "Rule::curly")] [INFO] [stdout] 108 | 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] --> step3/src/parse.rs:113:21 [INFO] [stdout] | [INFO] [stdout] 113 | #[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] 114 | #[pest(rule = "Rule::obj")] [INFO] [stdout] 115 | 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] --> step3b/src/parse.rs:17:21 [INFO] [stdout] | [INFO] [stdout] 17 | #[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] 18 | #[pest(rule = "Rule::int")] [INFO] [stdout] 19 | 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] --> step3b/src/parse.rs:25:21 [INFO] [stdout] | [INFO] [stdout] 25 | #[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] 26 | #[pest(rule = "Rule::symbol")] [INFO] [stdout] 27 | 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] --> step3b/src/parse.rs:31:21 [INFO] [stdout] | [INFO] [stdout] 31 | #[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] 32 | #[pest(rule = "Rule::kw")] [INFO] [stdout] 33 | 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] --> step3b/src/parse.rs:37:21 [INFO] [stdout] | [INFO] [stdout] 37 | #[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] 38 | #[pest(rule = "Rule::atom")] [INFO] [stdout] 39 | 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] --> step3b/src/parse.rs:43:21 [INFO] [stdout] | [INFO] [stdout] 43 | #[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] 44 | #[pest(rule = "Rule::strlit")] [INFO] [stdout] 45 | 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] --> step3b/src/parse.rs:49:21 [INFO] [stdout] | [INFO] [stdout] 49 | #[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] 50 | #[pest(rule = "Rule::quote")] [INFO] [stdout] 51 | 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] [stderr] Checking malvi_step8 v0.1.0 (/opt/rustwide/workdir/step8) [INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item [INFO] [stdout] --> step3b/src/parse.rs:56:21 [INFO] [stdout] | [INFO] [stdout] 56 | #[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] 57 | #[pest(rule = "Rule::quasiquote")] [INFO] [stdout] 58 | 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] --> step3b/src/parse.rs:63:21 [INFO] [stdout] | [INFO] [stdout] 63 | #[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] 64 | #[pest(rule = "Rule::unquote")] [INFO] [stdout] 65 | 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] --> step3b/src/parse.rs:70:21 [INFO] [stdout] | [INFO] [stdout] 70 | #[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] 71 | #[pest(rule = "Rule::spliceunquote")] [INFO] [stdout] 72 | 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] --> step3b/src/parse.rs:77:21 [INFO] [stdout] | [INFO] [stdout] 77 | #[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] 78 | #[pest(rule = "Rule::deref")] [INFO] [stdout] 79 | 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] --> step3b/src/parse.rs:84:21 [INFO] [stdout] | [INFO] [stdout] 84 | #[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] 85 | #[pest(rule = "Rule::withmeta")] [INFO] [stdout] 86 | 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] --> step3b/src/parse.rs:92:21 [INFO] [stdout] | [INFO] [stdout] 92 | #[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] 93 | #[pest(rule = "Rule::round")] [INFO] [stdout] 94 | 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] --> step3b/src/parse.rs:99:21 [INFO] [stdout] | [INFO] [stdout] 99 | #[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] 100 | #[pest(rule = "Rule::square")] [INFO] [stdout] 101 | 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] --> step3b/src/parse.rs:106:21 [INFO] [stdout] | [INFO] [stdout] 106 | #[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] 107 | #[pest(rule = "Rule::curly_item")] [INFO] [stdout] 108 | 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] --> step3b/src/parse.rs:114:21 [INFO] [stdout] | [INFO] [stdout] 114 | #[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] 115 | #[pest(rule = "Rule::curly")] [INFO] [stdout] 116 | 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] --> step3b/src/parse.rs:121:21 [INFO] [stdout] | [INFO] [stdout] 121 | #[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] 122 | #[pest(rule = "Rule::obj_simple")] [INFO] [stdout] 123 | 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] --> step3b/src/parse.rs:131:21 [INFO] [stdout] | [INFO] [stdout] 131 | #[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] 132 | #[pest(rule = "Rule::obj")] [INFO] [stdout] 133 | 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] --> step9/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] --> step9/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] --> step9/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] --> step9/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] --> step9/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] --> step9/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] --> step9/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] --> step9/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] --> step9/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] --> step9/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] --> step9/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] --> step9/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] --> step9/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] --> step9/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] --> step9/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] --> step9/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] --> step9/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] --> step9/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: 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] [stderr] Checking malvi_step3d v0.1.0 (/opt/rustwide/workdir/step3d) [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] --> step5/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] --> step5/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] --> step5/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] --> step5/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] --> step5/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] --> step5/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] --> step5/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] --> step5/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] --> step5/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] --> step5/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] --> step5/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] --> step5/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] --> step5/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] --> step5/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] --> step5/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] --> step5/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] --> step5/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] --> step5/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] --> step5/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] --> step5/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] --> step5/src/lib.rs:112:16 [INFO] [stdout] | [INFO] [stdout] 112 | 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] 112 | type Func = Rc>) -> Result>; [INFO] [stdout] | +++ [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] Checking malvi_step1 v0.1.0 (/opt/rustwide/workdir/step1) [INFO] [stderr] Checking malvi_step2b v0.1.0 (/opt/rustwide/workdir/step2b) [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] --> 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] --> step8/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] --> step8/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] --> step8/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] --> step8/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] --> step8/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] --> step8/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] --> step8/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] --> step8/src/stdfn_part3.rs:145:9 [INFO] [stdout] | [INFO] [stdout] 145 | /// 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] --> step8/src/stdfn_part3.rs:157:9 [INFO] [stdout] | [INFO] [stdout] 157 | /// 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: 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] --> step3d/src/parse.rs:26:21 [INFO] [stdout] | [INFO] [stdout] 26 | #[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] --> step3d/src/parse.rs:32:21 [INFO] [stdout] | [INFO] [stdout] 32 | #[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] --> step3d/src/parse.rs:38:21 [INFO] [stdout] | [INFO] [stdout] 38 | #[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] --> step3d/src/parse.rs:44:21 [INFO] [stdout] | [INFO] [stdout] 44 | #[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] --> step3d/src/parse.rs:50:21 [INFO] [stdout] | [INFO] [stdout] 50 | #[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] --> step3d/src/parse.rs:57:21 [INFO] [stdout] | [INFO] [stdout] 57 | #[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] --> step3d/src/parse.rs:64:21 [INFO] [stdout] | [INFO] [stdout] 64 | #[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] --> step3d/src/parse.rs:71:21 [INFO] [stdout] | [INFO] [stdout] 71 | #[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] --> step3d/src/parse.rs:78:21 [INFO] [stdout] | [INFO] [stdout] 78 | #[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] --> step3d/src/parse.rs:85:21 [INFO] [stdout] | [INFO] [stdout] 85 | #[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] --> step3d/src/parse.rs:93:21 [INFO] [stdout] | [INFO] [stdout] 93 | #[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] --> step3d/src/parse.rs:100:21 [INFO] [stdout] | [INFO] [stdout] 100 | #[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] --> step3d/src/parse.rs:107:21 [INFO] [stdout] | [INFO] [stdout] 107 | #[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] --> step3d/src/parse.rs:115:21 [INFO] [stdout] | [INFO] [stdout] 115 | #[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] --> step3d/src/parse.rs:122:21 [INFO] [stdout] | [INFO] [stdout] 122 | #[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] --> step3d/src/parse.rs:132:21 [INFO] [stdout] | [INFO] [stdout] 132 | #[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 `bind_by_move_pattern_guards` has been stable since 1.39.0 and no longer requires an attribute to enable [INFO] [stdout] --> step8/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] --> step8/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] --> step8/src/lib.rs:3:12 [INFO] [stdout] | [INFO] [stdout] 3 | #![feature(str_escape)] [INFO] [stdout] | ^^^^^^^^^^ [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: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: trait objects without an explicit `dyn` are deprecated [INFO] [stdout] --> step8/src/lib.rs:120:16 [INFO] [stdout] | [INFO] [stdout] 120 | 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] 120 | type Func = Rc>) -> Result>; [INFO] [stdout] | +++ [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] [stderr] Checking malvi_step2c v0.1.0 (/opt/rustwide/workdir/step2c) [INFO] [stdout] warning: the feature `chunks_exact` has been stable since 1.31.0 and no longer requires an attribute to enable [INFO] [stdout] --> step3d/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] --> step3d/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] --> step3d/src/lib.rs:75:16 [INFO] [stdout] | [INFO] [stdout] 75 | 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] 75 | type Func = Rc>) -> Result>; [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step1/src/parse.rs:12:21 [INFO] [stdout] | [INFO] [stdout] 12 | #[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] --> step1/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: 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] --> step1/src/parse.rs:26:21 [INFO] [stdout] | [INFO] [stdout] 26 | #[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] --> step1/src/parse.rs:32:21 [INFO] [stdout] | [INFO] [stdout] 32 | #[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] --> step1/src/parse.rs:38:21 [INFO] [stdout] | [INFO] [stdout] 38 | #[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] --> step1/src/parse.rs:44:21 [INFO] [stdout] | [INFO] [stdout] 44 | #[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] --> step1/src/parse.rs:51:21 [INFO] [stdout] | [INFO] [stdout] 51 | #[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] --> step1/src/parse.rs:58:21 [INFO] [stdout] | [INFO] [stdout] 58 | #[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] --> step1/src/parse.rs:65:21 [INFO] [stdout] | [INFO] [stdout] 65 | #[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] --> step1/src/parse.rs:72:21 [INFO] [stdout] | [INFO] [stdout] 72 | #[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] --> step1/src/parse.rs:79:21 [INFO] [stdout] | [INFO] [stdout] 79 | #[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] --> step1/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] --> step1/src/parse.rs:94:21 [INFO] [stdout] | [INFO] [stdout] 94 | #[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] --> step1/src/parse.rs:101:21 [INFO] [stdout] | [INFO] [stdout] 101 | #[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] --> step1/src/parse.rs:108:21 [INFO] [stdout] | [INFO] [stdout] 108 | #[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 `std::result::Result` that must be used [INFO] [stdout] --> step5/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] --> step5/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] --> step5/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] --> step5/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] --> step5/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] --> step5/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] --> step5/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()), env, dm), [INFO] [stdout] 274 | | BoundAstRef(v, env, 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] --> step5/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] --> step5/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] --> step5/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] --> step5/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] --> step5/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] --> step5/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] --> step5/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] --> step5/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] --> step5/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] --> step5/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] --> step5/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] --> step5/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] --> step5/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] --> step5/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] --> step5/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] --> step5/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] --> step5/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] --> step5/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] --> step5/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] --> step5/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] --> step5/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] Checking malvi_stepA v0.1.0 (/opt/rustwide/workdir/stepA) [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step2b/src/parse.rs:16:21 [INFO] [stdout] | [INFO] [stdout] 16 | #[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] --> step2b/src/parse.rs:24:21 [INFO] [stdout] | [INFO] [stdout] 24 | #[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] --> step2b/src/parse.rs:30:21 [INFO] [stdout] | [INFO] [stdout] 30 | #[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] --> step2b/src/parse.rs:36:21 [INFO] [stdout] | [INFO] [stdout] 36 | #[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] --> step2b/src/parse.rs:42:21 [INFO] [stdout] | [INFO] [stdout] 42 | #[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] --> step2b/src/parse.rs:48:21 [INFO] [stdout] | [INFO] [stdout] 48 | #[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] --> step2b/src/parse.rs:55:21 [INFO] [stdout] | [INFO] [stdout] 55 | #[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] --> step2c/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] --> step2b/src/parse.rs:62:21 [INFO] [stdout] | [INFO] [stdout] 62 | #[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] --> step2b/src/parse.rs:69:21 [INFO] [stdout] | [INFO] [stdout] 69 | #[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] --> step2b/src/parse.rs:76:21 [INFO] [stdout] | [INFO] [stdout] 76 | #[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] --> step2c/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] --> step2c/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] --> step2c/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] --> step2b/src/parse.rs:83:21 [INFO] [stdout] | [INFO] [stdout] 83 | #[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] --> step2b/src/parse.rs:91:21 [INFO] [stdout] | [INFO] [stdout] 91 | #[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] --> step2b/src/parse.rs:98:21 [INFO] [stdout] | [INFO] [stdout] 98 | #[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] --> step2b/src/parse.rs:105:21 [INFO] [stdout] | [INFO] [stdout] 105 | #[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] --> step2b/src/parse.rs:112:21 [INFO] [stdout] | [INFO] [stdout] 112 | #[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] --> step2c/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] --> step2c/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] --> step2c/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] --> step2c/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] --> step2c/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] --> step2c/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] --> step2c/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] --> step2c/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] --> step2c/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] --> step2c/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] --> step2c/src/parse.rs:113:21 [INFO] [stdout] | [INFO] [stdout] 113 | #[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 `std::result::Result` that must be used [INFO] [stdout] --> step8/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: the feature `convert_id` has been stable since 1.33.0 and no longer requires an attribute to enable [INFO] [stdout] --> step2c/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: trait objects without an explicit `dyn` are deprecated [INFO] [stdout] --> step2b/src/lib.rs:73:17 [INFO] [stdout] | [INFO] [stdout] 73 | type Func = Box 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] 73 | type Func = Box Result>; [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `std::result::Result` that must be used [INFO] [stdout] --> step8/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] --> step8/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] --> step8/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] --> step8/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] --> step8/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] --> step8/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: trait objects without an explicit `dyn` are deprecated [INFO] [stdout] --> step2c/src/lib.rs:66:17 [INFO] [stdout] | [INFO] [stdout] 66 | type Func = Box 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] 66 | type Func = Box Result>; [INFO] [stdout] | +++ [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] --> step8/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] --> step8/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] --> step8/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] --> step8/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] --> step8/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] --> step8/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] --> step8/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] --> step8/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] --> step8/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] --> step8/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] --> step8/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] --> step8/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] --> step8/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] --> step8/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] --> step8/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] --> step8/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] --> step8/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] --> step8/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] --> step8/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] --> step8/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] --> step8/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] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item [INFO] [stdout] --> final/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] --> final/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] --> final/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] --> final/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] --> final/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] --> final/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] --> final/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] --> final/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] --> final/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] --> final/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] --> final/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] --> final/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] --> final/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] --> final/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] --> final/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] --> final/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] --> final/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] --> final/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] --> step6/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] --> step6/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] --> step6/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] --> step6/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] --> step6/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] --> step6/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] --> step6/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] --> step6/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] --> step6/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] --> step6/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] --> step6/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] --> step6/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] --> step6/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] --> step6/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] --> step6/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] --> step6/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] --> step6/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] --> step6/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] --> step6/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] --> step6/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] --> step6/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] --> step6/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] --> step6/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] --> step6/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] --> step6/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] --> step6/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] --> step6/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] --> step6/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] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item [INFO] [stdout] --> step2b/src/parse.rs:16:21 [INFO] [stdout] | [INFO] [stdout] 16 | #[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] 17 | #[pest(rule = "Rule::int")] [INFO] [stdout] 18 | 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] --> step2b/src/parse.rs:24:21 [INFO] [stdout] | [INFO] [stdout] 24 | #[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] 25 | #[pest(rule = "Rule::symbol")] [INFO] [stdout] 26 | 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] --> step2b/src/parse.rs:30:21 [INFO] [stdout] | [INFO] [stdout] 30 | #[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] 31 | #[pest(rule = "Rule::kw")] [INFO] [stdout] 32 | 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] --> step2b/src/parse.rs:36:21 [INFO] [stdout] | [INFO] [stdout] 36 | #[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] 37 | #[pest(rule = "Rule::atom")] [INFO] [stdout] 38 | 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] --> step2b/src/parse.rs:42:21 [INFO] [stdout] | [INFO] [stdout] 42 | #[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] 43 | #[pest(rule = "Rule::strlit")] [INFO] [stdout] 44 | 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] --> step2b/src/parse.rs:48:21 [INFO] [stdout] | [INFO] [stdout] 48 | #[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] 49 | #[pest(rule = "Rule::quote")] [INFO] [stdout] 50 | 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] --> step2b/src/parse.rs:55:21 [INFO] [stdout] | [INFO] [stdout] 55 | #[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] 56 | #[pest(rule = "Rule::quasiquote")] [INFO] [stdout] 57 | 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] --> step2b/src/parse.rs:62:21 [INFO] [stdout] | [INFO] [stdout] 62 | #[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] 63 | #[pest(rule = "Rule::unquote")] [INFO] [stdout] 64 | 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] --> step2b/src/parse.rs:69:21 [INFO] [stdout] | [INFO] [stdout] 69 | #[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] 70 | #[pest(rule = "Rule::spliceunquote")] [INFO] [stdout] 71 | 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] --> step2b/src/parse.rs:76:21 [INFO] [stdout] | [INFO] [stdout] 76 | #[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] 77 | #[pest(rule = "Rule::deref")] [INFO] [stdout] 78 | 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] --> step2b/src/parse.rs:83:21 [INFO] [stdout] | [INFO] [stdout] 83 | #[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] 84 | #[pest(rule = "Rule::withmeta")] [INFO] [stdout] 85 | 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] --> step2b/src/parse.rs:91:21 [INFO] [stdout] | [INFO] [stdout] 91 | #[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] 92 | #[pest(rule = "Rule::round")] [INFO] [stdout] 93 | 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] --> step2b/src/parse.rs:98:21 [INFO] [stdout] | [INFO] [stdout] 98 | #[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] 99 | #[pest(rule = "Rule::square")] [INFO] [stdout] 100 | 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] --> step2b/src/parse.rs:105:21 [INFO] [stdout] | [INFO] [stdout] 105 | #[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] 106 | #[pest(rule = "Rule::curly")] [INFO] [stdout] 107 | 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] --> step2b/src/parse.rs:112:21 [INFO] [stdout] | [INFO] [stdout] 112 | #[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] 113 | #[pest(rule = "Rule::obj")] [INFO] [stdout] 114 | 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: 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: non-local `impl` definition, `impl` blocks should be written at the same level as their item [INFO] [stdout] --> step1/src/parse.rs:12:21 [INFO] [stdout] | [INFO] [stdout] 12 | #[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] 13 | #[pest(rule = "Rule::int")] [INFO] [stdout] 14 | 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] --> step1/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_Symbol` [INFO] [stdout] 21 | #[pest(rule = "Rule::symbol")] [INFO] [stdout] 22 | 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] --> step1/src/parse.rs:26:21 [INFO] [stdout] | [INFO] [stdout] 26 | #[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] 27 | #[pest(rule = "Rule::kw")] [INFO] [stdout] 28 | 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] --> step1/src/parse.rs:32:21 [INFO] [stdout] | [INFO] [stdout] 32 | #[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] 33 | #[pest(rule = "Rule::atom")] [INFO] [stdout] 34 | 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] --> step1/src/parse.rs:38:21 [INFO] [stdout] | [INFO] [stdout] 38 | #[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] 39 | #[pest(rule = "Rule::strlit")] [INFO] [stdout] 40 | 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] --> step1/src/parse.rs:44:21 [INFO] [stdout] | [INFO] [stdout] 44 | #[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] 45 | #[pest(rule = "Rule::quote")] [INFO] [stdout] 46 | 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] --> step1/src/parse.rs:51:21 [INFO] [stdout] | [INFO] [stdout] 51 | #[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] 52 | #[pest(rule = "Rule::quasiquote")] [INFO] [stdout] 53 | 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] --> step1/src/parse.rs:58:21 [INFO] [stdout] | [INFO] [stdout] 58 | #[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] 59 | #[pest(rule = "Rule::unquote")] [INFO] [stdout] 60 | 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] --> step1/src/parse.rs:65:21 [INFO] [stdout] | [INFO] [stdout] 65 | #[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] 66 | #[pest(rule = "Rule::spliceunquote")] [INFO] [stdout] 67 | 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] --> step1/src/parse.rs:72:21 [INFO] [stdout] | [INFO] [stdout] 72 | #[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] 73 | #[pest(rule = "Rule::deref")] [INFO] [stdout] 74 | 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] --> step1/src/parse.rs:79:21 [INFO] [stdout] | [INFO] [stdout] 79 | #[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] 80 | #[pest(rule = "Rule::withmeta")] [INFO] [stdout] 81 | 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] --> step1/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_Round` [INFO] [stdout] 88 | #[pest(rule = "Rule::round")] [INFO] [stdout] 89 | 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] --> step1/src/parse.rs:94:21 [INFO] [stdout] | [INFO] [stdout] 94 | #[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] 95 | #[pest(rule = "Rule::square")] [INFO] [stdout] 96 | 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] --> step1/src/parse.rs:101:21 [INFO] [stdout] | [INFO] [stdout] 101 | #[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] 102 | #[pest(rule = "Rule::curly")] [INFO] [stdout] 103 | 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] --> step1/src/parse.rs:108:21 [INFO] [stdout] | [INFO] [stdout] 108 | #[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] 109 | #[pest(rule = "Rule::obj")] [INFO] [stdout] 110 | 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] --> step3d/src/parse.rs:18:21 [INFO] [stdout] | [INFO] [stdout] 18 | #[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] 19 | #[pest(rule = "Rule::int")] [INFO] [stdout] 20 | 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] --> step3d/src/parse.rs:26:21 [INFO] [stdout] | [INFO] [stdout] 26 | #[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] 27 | #[pest(rule = "Rule::symbol")] [INFO] [stdout] 28 | 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] --> step3d/src/parse.rs:32:21 [INFO] [stdout] | [INFO] [stdout] 32 | #[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] 33 | #[pest(rule = "Rule::kw")] [INFO] [stdout] 34 | 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] --> step3d/src/parse.rs:38:21 [INFO] [stdout] | [INFO] [stdout] 38 | #[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] 39 | #[pest(rule = "Rule::atom")] [INFO] [stdout] 40 | 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] --> step3d/src/parse.rs:44:21 [INFO] [stdout] | [INFO] [stdout] 44 | #[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] 45 | #[pest(rule = "Rule::strlit")] [INFO] [stdout] 46 | 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] --> step3d/src/parse.rs:50:21 [INFO] [stdout] | [INFO] [stdout] 50 | #[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] 51 | #[pest(rule = "Rule::quote")] [INFO] [stdout] 52 | 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] --> step3d/src/parse.rs:57:21 [INFO] [stdout] | [INFO] [stdout] 57 | #[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] 58 | #[pest(rule = "Rule::quasiquote")] [INFO] [stdout] 59 | 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] --> step3d/src/parse.rs:64:21 [INFO] [stdout] | [INFO] [stdout] 64 | #[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] 65 | #[pest(rule = "Rule::unquote")] [INFO] [stdout] 66 | 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: 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] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item [INFO] [stdout] --> step3d/src/parse.rs:71:21 [INFO] [stdout] | [INFO] [stdout] 71 | #[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] 72 | #[pest(rule = "Rule::spliceunquote")] [INFO] [stdout] 73 | 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] --> step3d/src/parse.rs:78:21 [INFO] [stdout] | [INFO] [stdout] 78 | #[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] 79 | #[pest(rule = "Rule::deref")] [INFO] [stdout] 80 | 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] --> step3d/src/parse.rs:85:21 [INFO] [stdout] | [INFO] [stdout] 85 | #[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] 86 | #[pest(rule = "Rule::withmeta")] [INFO] [stdout] 87 | 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] --> step3d/src/parse.rs:93:21 [INFO] [stdout] | [INFO] [stdout] 93 | #[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] 94 | #[pest(rule = "Rule::round")] [INFO] [stdout] 95 | 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] --> step3d/src/parse.rs:100:21 [INFO] [stdout] | [INFO] [stdout] 100 | #[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] 101 | #[pest(rule = "Rule::square")] [INFO] [stdout] 102 | 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] --> step3d/src/parse.rs:107:21 [INFO] [stdout] | [INFO] [stdout] 107 | #[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] 108 | #[pest(rule = "Rule::curly_item")] [INFO] [stdout] 109 | 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] --> step3d/src/parse.rs:115:21 [INFO] [stdout] | [INFO] [stdout] 115 | #[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] 116 | #[pest(rule = "Rule::curly")] [INFO] [stdout] 117 | 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] --> step3d/src/parse.rs:122:21 [INFO] [stdout] | [INFO] [stdout] 122 | #[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] 123 | #[pest(rule = "Rule::obj_simple")] [INFO] [stdout] 124 | 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] --> step3d/src/parse.rs:132:21 [INFO] [stdout] | [INFO] [stdout] 132 | #[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] 133 | #[pest(rule = "Rule::obj")] [INFO] [stdout] 134 | 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] --> step2c/src/parse.rs:17:21 [INFO] [stdout] | [INFO] [stdout] 17 | #[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] 18 | #[pest(rule = "Rule::int")] [INFO] [stdout] 19 | 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] --> step2c/src/parse.rs:25:21 [INFO] [stdout] | [INFO] [stdout] 25 | #[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] 26 | #[pest(rule = "Rule::symbol")] [INFO] [stdout] 27 | 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] --> step2c/src/parse.rs:31:21 [INFO] [stdout] | [INFO] [stdout] 31 | #[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] 32 | #[pest(rule = "Rule::kw")] [INFO] [stdout] 33 | 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] --> step2c/src/parse.rs:37:21 [INFO] [stdout] | [INFO] [stdout] 37 | #[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] 38 | #[pest(rule = "Rule::atom")] [INFO] [stdout] 39 | 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] --> step2c/src/parse.rs:43:21 [INFO] [stdout] | [INFO] [stdout] 43 | #[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] 44 | #[pest(rule = "Rule::strlit")] [INFO] [stdout] 45 | 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] --> step2c/src/parse.rs:49:21 [INFO] [stdout] | [INFO] [stdout] 49 | #[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] 50 | #[pest(rule = "Rule::quote")] [INFO] [stdout] 51 | 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] --> step2c/src/parse.rs:56:21 [INFO] [stdout] | [INFO] [stdout] 56 | #[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] 57 | #[pest(rule = "Rule::quasiquote")] [INFO] [stdout] 58 | 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] --> step2c/src/parse.rs:63:21 [INFO] [stdout] | [INFO] [stdout] 63 | #[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] 64 | #[pest(rule = "Rule::unquote")] [INFO] [stdout] 65 | 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] --> step2c/src/parse.rs:70:21 [INFO] [stdout] | [INFO] [stdout] 70 | #[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] 71 | #[pest(rule = "Rule::spliceunquote")] [INFO] [stdout] 72 | 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] --> step2c/src/parse.rs:77:21 [INFO] [stdout] | [INFO] [stdout] 77 | #[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] 78 | #[pest(rule = "Rule::deref")] [INFO] [stdout] 79 | 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] --> step2c/src/parse.rs:84:21 [INFO] [stdout] | [INFO] [stdout] 84 | #[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] 85 | #[pest(rule = "Rule::withmeta")] [INFO] [stdout] 86 | 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] --> step2c/src/parse.rs:92:21 [INFO] [stdout] | [INFO] [stdout] 92 | #[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] 93 | #[pest(rule = "Rule::round")] [INFO] [stdout] 94 | 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] --> step2c/src/parse.rs:99:21 [INFO] [stdout] | [INFO] [stdout] 99 | #[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] 100 | #[pest(rule = "Rule::square")] [INFO] [stdout] 101 | 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] --> step2c/src/parse.rs:106:21 [INFO] [stdout] | [INFO] [stdout] 106 | #[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] 107 | #[pest(rule = "Rule::curly")] [INFO] [stdout] 108 | 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] --> step2c/src/parse.rs:113:21 [INFO] [stdout] | [INFO] [stdout] 113 | #[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] 114 | #[pest(rule = "Rule::obj")] [INFO] [stdout] 115 | 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: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> step2c/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] --> step2c/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] --> step2c/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] --> step2c/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] --> step2c/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] --> step2c/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] --> step2c/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] --> step2c/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] --> step2c/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] --> step2c/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] --> step2c/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] --> step2c/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] --> step2c/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] --> step2c/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] --> step2c/src/parse.rs:113:21 [INFO] [stdout] | [INFO] [stdout] 113 | #[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] --> step2c/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: trait objects without an explicit `dyn` are deprecated [INFO] [stdout] --> step2c/src/lib.rs:66:17 [INFO] [stdout] | [INFO] [stdout] 66 | type Func = Box 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] 66 | type Func = Box Result>; [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [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] [WARN] too many lines in the log, truncating it