[INFO] cloning repository https://github.com/lise-henry/rscheme [INFO] running `Command { std: "git" "-c" "credential.helper=" "-c" "credential.helper=/workspace/cargo-home/bin/git-credential-null" "clone" "--bare" "https://github.com/lise-henry/rscheme" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Flise-henry%2Frscheme", kill_on_drop: false }` [INFO] [stderr] Cloning into bare repository '/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Flise-henry%2Frscheme'... [INFO] running `Command { std: "git" "rev-parse" "HEAD", kill_on_drop: false }` [INFO] [stdout] af30c24aa7a25b9d8bd71703a2650384b4aa8cbb [INFO] building lise-henry/rscheme against try#9b5e8b16bd1c4acf4cf8e6880368314cf021a987+rustflags=-Dtail-expr-drop-order for pr-134523 [INFO] running `Command { std: "git" "clone" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Flise-henry%2Frscheme" "/workspace/builds/worker-4-tc2/source", kill_on_drop: false }` [INFO] [stderr] Cloning into '/workspace/builds/worker-4-tc2/source'... [INFO] [stderr] done. [INFO] validating manifest of git repo https://github.com/lise-henry/rscheme on toolchain 9b5e8b16bd1c4acf4cf8e6880368314cf021a987 [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+9b5e8b16bd1c4acf4cf8e6880368314cf021a987" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] started tweaking git repo https://github.com/lise-henry/rscheme [INFO] finished tweaking git repo https://github.com/lise-henry/rscheme [INFO] tweaked toml for git repo https://github.com/lise-henry/rscheme written to /workspace/builds/worker-4-tc2/source/Cargo.toml [INFO] crate git repo https://github.com/lise-henry/rscheme 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" "+9b5e8b16bd1c4acf4cf8e6880368314cf021a987" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] warning: no edition set: defaulting to the 2015 edition while the latest is 2024 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:f3a9d4ad9d972b27faf3965f35b62e55ba32bbce8f20bc8fe909558a86702fde" "/opt/rustwide/cargo-home/bin/cargo" "+9b5e8b16bd1c4acf4cf8e6880368314cf021a987" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] 4815f6c8c613950d404f373f90230b4d4b79df2d4ecbc9f8f8307974466ec09b [INFO] running `Command { std: "docker" "start" "-a" "4815f6c8c613950d404f373f90230b4d4b79df2d4ecbc9f8f8307974466ec09b", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "4815f6c8c613950d404f373f90230b4d4b79df2d4ecbc9f8f8307974466ec09b", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "4815f6c8c613950d404f373f90230b4d4b79df2d4ecbc9f8f8307974466ec09b", kill_on_drop: false }` [INFO] [stdout] 4815f6c8c613950d404f373f90230b4d4b79df2d4ecbc9f8f8307974466ec09b [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid -Dtail-expr-drop-order" "-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:f3a9d4ad9d972b27faf3965f35b62e55ba32bbce8f20bc8fe909558a86702fde" "/opt/rustwide/cargo-home/bin/cargo" "+9b5e8b16bd1c4acf4cf8e6880368314cf021a987" "build" "--frozen" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] 2eec89ea83a730ec251abd46cb2e4b9df41afed426f292bccdd775e1215421e1 [INFO] running `Command { std: "docker" "start" "-a" "2eec89ea83a730ec251abd46cb2e4b9df41afed426f292bccdd775e1215421e1", kill_on_drop: false }` [INFO] [stderr] warning: no edition set: defaulting to the 2015 edition while the latest is 2024 [INFO] [stderr] Compiling libc v0.1.8 [INFO] [stderr] Compiling log v0.3.1 [INFO] [stderr] Compiling rscheme v1.0.0 (/opt/rustwide/workdir) [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/lexer.rs:77:29 [INFO] [stdout] | [INFO] [stdout] 77 | ... error!("Mismatched parenthesis: too many )s"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: expected names are: `clippy`, `debug_assertions`, `doc`, `docsrs`, `doctest`, `feature`, `fmt_debug`, `miri`, `overflow_checks`, `panic`, `proc_macro`, `relocation_model`, `rustfmt`, `sanitize`, `sanitizer_cfi_generalize_pointers`, `sanitizer_cfi_normalize_integers`, `target_abi`, `target_arch`, `target_endian`, `target_env`, `target_family`, `target_feature`, `target_has_atomic`, `target_has_atomic_equal_alignment`, `target_has_atomic_load_store`, `target_os`, `target_pointer_width`, `target_thread_local`, `target_vendor`, `test`, `ub_checks`, `unix`, and `windows` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [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 macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/lexer.rs:77:29 [INFO] [stdout] | [INFO] [stdout] 77 | ... error!("Mismatched parenthesis: too many )s"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/lexer.rs:77:29 [INFO] [stdout] | [INFO] [stdout] 77 | ... error!("Mismatched parenthesis: too many )s"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/lexer.rs:77:29 [INFO] [stdout] | [INFO] [stdout] 77 | ... error!("Mismatched parenthesis: too many )s"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/lexer.rs:77:29 [INFO] [stdout] | [INFO] [stdout] 77 | ... error!("Mismatched parenthesis: too many )s"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `...` range patterns are deprecated [INFO] [stdout] --> src/lexer.rs:102:25 [INFO] [stdout] | [INFO] [stdout] 102 | '0' ... '9' => { [INFO] [stdout] | ^^^ help: use `..=` for an inclusive range [INFO] [stdout] | [INFO] [stdout] = warning: this is accepted in the current edition (Rust 2015) but is a hard error in Rust 2021! [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: `#[warn(ellipsis_inclusive_range_patterns)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/lexer.rs:130:21 [INFO] [stdout] | [INFO] [stdout] 130 | error!("Error parsing 'integer': {}", s.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/lexer.rs:130:21 [INFO] [stdout] | [INFO] [stdout] 130 | error!("Error parsing 'integer': {}", s.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/lexer.rs:130:21 [INFO] [stdout] | [INFO] [stdout] 130 | error!("Error parsing 'integer': {}", s.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/lexer.rs:130:21 [INFO] [stdout] | [INFO] [stdout] 130 | error!("Error parsing 'integer': {}", s.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/lexer.rs:130:21 [INFO] [stdout] | [INFO] [stdout] 130 | error!("Error parsing 'integer': {}", s.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/lexer.rs:138:21 [INFO] [stdout] | [INFO] [stdout] 138 | error!("Error parsing 'float': {}", s.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/lexer.rs:138:21 [INFO] [stdout] | [INFO] [stdout] 138 | error!("Error parsing 'float': {}", s.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/lexer.rs:138:21 [INFO] [stdout] | [INFO] [stdout] 138 | error!("Error parsing 'float': {}", s.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/lexer.rs:138:21 [INFO] [stdout] | [INFO] [stdout] 138 | error!("Error parsing 'float': {}", s.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/lexer.rs:138:21 [INFO] [stdout] | [INFO] [stdout] 138 | error!("Error parsing 'float': {}", s.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `...` range patterns are deprecated [INFO] [stdout] --> src/lexer.rs:159:17 [INFO] [stdout] | [INFO] [stdout] 159 | '0' ... '9' => { [INFO] [stdout] | ^^^ help: use `..=` for an inclusive range [INFO] [stdout] | [INFO] [stdout] = warning: this is accepted in the current edition (Rust 2015) but is a hard error in Rust 2021! [INFO] [stdout] = note: for more information, see [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/lexer.rs:170:21 [INFO] [stdout] | [INFO] [stdout] 170 | error!("Lexer: Invalid number: contains more than one dot"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/lexer.rs:170:21 [INFO] [stdout] | [INFO] [stdout] 170 | error!("Lexer: Invalid number: contains more than one dot"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/lexer.rs:170:21 [INFO] [stdout] | [INFO] [stdout] 170 | error!("Lexer: Invalid number: contains more than one dot"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/lexer.rs:170:21 [INFO] [stdout] | [INFO] [stdout] 170 | error!("Lexer: Invalid number: contains more than one dot"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/lexer.rs:170:21 [INFO] [stdout] | [INFO] [stdout] 170 | error!("Lexer: Invalid number: contains more than one dot"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/lexer.rs:176:17 [INFO] [stdout] | [INFO] [stdout] 176 | error!("Lexer: Invalid character in a number: {}", c); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/lexer.rs:176:17 [INFO] [stdout] | [INFO] [stdout] 176 | error!("Lexer: Invalid character in a number: {}", c); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/lexer.rs:176:17 [INFO] [stdout] | [INFO] [stdout] 176 | error!("Lexer: Invalid character in a number: {}", c); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/lexer.rs:176:17 [INFO] [stdout] | [INFO] [stdout] 176 | error!("Lexer: Invalid character in a number: {}", c); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/lexer.rs:176:17 [INFO] [stdout] | [INFO] [stdout] 176 | error!("Lexer: Invalid character in a number: {}", c); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/lexer.rs:184:17 [INFO] [stdout] | [INFO] [stdout] 184 | error!("Lexer error: can't find closing quote"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/lexer.rs:184:17 [INFO] [stdout] | [INFO] [stdout] 184 | error!("Lexer error: can't find closing quote"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/lexer.rs:184:17 [INFO] [stdout] | [INFO] [stdout] 184 | error!("Lexer error: can't find closing quote"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/lexer.rs:184:17 [INFO] [stdout] | [INFO] [stdout] 184 | error!("Lexer error: can't find closing quote"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/lexer.rs:184:17 [INFO] [stdout] | [INFO] [stdout] 184 | error!("Lexer error: can't find closing quote"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/lexer.rs:194:25 [INFO] [stdout] | [INFO] [stdout] 194 | error!("Lexer error: can't finish lexing string"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/lexer.rs:194:25 [INFO] [stdout] | [INFO] [stdout] 194 | error!("Lexer error: can't finish lexing string"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/lexer.rs:194:25 [INFO] [stdout] | [INFO] [stdout] 194 | error!("Lexer error: can't finish lexing string"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/lexer.rs:194:25 [INFO] [stdout] | [INFO] [stdout] 194 | error!("Lexer error: can't finish lexing string"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/lexer.rs:194:25 [INFO] [stdout] | [INFO] [stdout] 194 | error!("Lexer error: can't finish lexing string"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/lexer.rs:212:33 [INFO] [stdout] | [INFO] [stdout] 212 | ... error!("Unrecognized escape character \\{}", c2); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/lexer.rs:212:33 [INFO] [stdout] | [INFO] [stdout] 212 | ... error!("Unrecognized escape character \\{}", c2); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/lexer.rs:212:33 [INFO] [stdout] | [INFO] [stdout] 212 | ... error!("Unrecognized escape character \\{}", c2); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/lexer.rs:212:33 [INFO] [stdout] | [INFO] [stdout] 212 | ... error!("Unrecognized escape character \\{}", c2); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/lexer.rs:212:33 [INFO] [stdout] | [INFO] [stdout] 212 | ... error!("Unrecognized escape character \\{}", c2); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/read.rs:19:9 [INFO] [stdout] | [INFO] [stdout] 19 | error! ("Error parsing quote: not enough arguments"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/read.rs:19:9 [INFO] [stdout] | [INFO] [stdout] 19 | error! ("Error parsing quote: not enough arguments"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/read.rs:19:9 [INFO] [stdout] | [INFO] [stdout] 19 | error! ("Error parsing quote: not enough arguments"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/read.rs:19:9 [INFO] [stdout] | [INFO] [stdout] 19 | error! ("Error parsing quote: not enough arguments"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/read.rs:19:9 [INFO] [stdout] | [INFO] [stdout] 19 | error! ("Error parsing quote: not enough arguments"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/read.rs:29:9 [INFO] [stdout] | [INFO] [stdout] 29 | error! ("Error parsing quote: not enough arguments"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/read.rs:29:9 [INFO] [stdout] | [INFO] [stdout] 29 | error! ("Error parsing quote: not enough arguments"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/read.rs:29:9 [INFO] [stdout] | [INFO] [stdout] 29 | error! ("Error parsing quote: not enough arguments"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/read.rs:29:9 [INFO] [stdout] | [INFO] [stdout] 29 | error! ("Error parsing quote: not enough arguments"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/read.rs:29:9 [INFO] [stdout] | [INFO] [stdout] 29 | error! ("Error parsing quote: not enough arguments"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/read.rs:39:9 [INFO] [stdout] | [INFO] [stdout] 39 | error! ("Error parsing quote: not enough arguments"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/read.rs:39:9 [INFO] [stdout] | [INFO] [stdout] 39 | error! ("Error parsing quote: not enough arguments"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/read.rs:39:9 [INFO] [stdout] | [INFO] [stdout] 39 | error! ("Error parsing quote: not enough arguments"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/read.rs:39:9 [INFO] [stdout] | [INFO] [stdout] 39 | error! ("Error parsing quote: not enough arguments"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/read.rs:39:9 [INFO] [stdout] | [INFO] [stdout] 39 | error! ("Error parsing quote: not enough arguments"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/read.rs:49:9 [INFO] [stdout] | [INFO] [stdout] 49 | error! ("Error parsing '(: closing parenthesis not found"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/read.rs:49:9 [INFO] [stdout] | [INFO] [stdout] 49 | error! ("Error parsing '(: closing parenthesis not found"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/read.rs:49:9 [INFO] [stdout] | [INFO] [stdout] 49 | error! ("Error parsing '(: closing parenthesis not found"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/read.rs:49:9 [INFO] [stdout] | [INFO] [stdout] 49 | error! ("Error parsing '(: closing parenthesis not found"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/read.rs:49:9 [INFO] [stdout] | [INFO] [stdout] 49 | error! ("Error parsing '(: closing parenthesis not found"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/read.rs:77:13 [INFO] [stdout] | [INFO] [stdout] 77 | error!("Parse error: closing parenthesis doesn't match opening one"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/read.rs:77:13 [INFO] [stdout] | [INFO] [stdout] 77 | error!("Parse error: closing parenthesis doesn't match opening one"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/read.rs:77:13 [INFO] [stdout] | [INFO] [stdout] 77 | error!("Parse error: closing parenthesis doesn't match opening one"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/read.rs:77:13 [INFO] [stdout] | [INFO] [stdout] 77 | error!("Parse error: closing parenthesis doesn't match opening one"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/read.rs:77:13 [INFO] [stdout] | [INFO] [stdout] 77 | error!("Parse error: closing parenthesis doesn't match opening one"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/read.rs:118:13 [INFO] [stdout] | [INFO] [stdout] 118 | error!("Error opening file {}", s); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/read.rs:118:13 [INFO] [stdout] | [INFO] [stdout] 118 | error!("Error opening file {}", s); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/read.rs:118:13 [INFO] [stdout] | [INFO] [stdout] 118 | error!("Error opening file {}", s); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/read.rs:118:13 [INFO] [stdout] | [INFO] [stdout] 118 | error!("Error opening file {}", s); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/read.rs:118:13 [INFO] [stdout] | [INFO] [stdout] 118 | error!("Error opening file {}", s); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unnecessary parentheses around function argument [INFO] [stdout] --> src/eval.rs:86:39 [INFO] [stdout] | [INFO] [stdout] 86 | env: Rc::new(RefCell::new((HashMap::new()))), [INFO] [stdout] | ^ ^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(unused_parens)]` on by default [INFO] [stdout] help: remove these parentheses [INFO] [stdout] | [INFO] [stdout] 86 - env: Rc::new(RefCell::new((HashMap::new()))), [INFO] [stdout] 86 + env: Rc::new(RefCell::new(HashMap::new())), [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unnecessary parentheses around function argument [INFO] [stdout] --> src/eval.rs:87:46 [INFO] [stdout] | [INFO] [stdout] 87 | global_env: Rc::new(RefCell::new((HashMap::new()))), [INFO] [stdout] | ^ ^ [INFO] [stdout] | [INFO] [stdout] help: remove these parentheses [INFO] [stdout] | [INFO] [stdout] 87 - global_env: Rc::new(RefCell::new((HashMap::new()))), [INFO] [stdout] 87 + global_env: Rc::new(RefCell::new(HashMap::new())), [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:99:9 [INFO] [stdout] | [INFO] [stdout] 99 | error!("{}", s); [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:99:9 [INFO] [stdout] | [INFO] [stdout] 99 | error!("{}", s); [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:99:9 [INFO] [stdout] | [INFO] [stdout] 99 | error!("{}", s); [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:99:9 [INFO] [stdout] | [INFO] [stdout] 99 | error!("{}", s); [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:99:9 [INFO] [stdout] | [INFO] [stdout] 99 | error!("{}", s); [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:126:25 [INFO] [stdout] | [INFO] [stdout] 126 | error!("Lookup: variable {} not found in environment", ident); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:126:25 [INFO] [stdout] | [INFO] [stdout] 126 | error!("Lookup: variable {} not found in environment", ident); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:126:25 [INFO] [stdout] | [INFO] [stdout] 126 | error!("Lookup: variable {} not found in environment", ident); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:126:25 [INFO] [stdout] | [INFO] [stdout] 126 | error!("Lookup: variable {} not found in environment", ident); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:126:25 [INFO] [stdout] | [INFO] [stdout] 126 | error!("Lookup: variable {} not found in environment", ident); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:147:13 [INFO] [stdout] | [INFO] [stdout] 147 | error!("Keyword {} is reserved", ident); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:147:13 [INFO] [stdout] | [INFO] [stdout] 147 | error!("Keyword {} is reserved", ident); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:147:13 [INFO] [stdout] | [INFO] [stdout] 147 | error!("Keyword {} is reserved", ident); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:147:13 [INFO] [stdout] | [INFO] [stdout] 147 | error!("Keyword {} is reserved", ident); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:147:13 [INFO] [stdout] | [INFO] [stdout] 147 | error!("Keyword {} is reserved", ident); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:158:13 [INFO] [stdout] | [INFO] [stdout] 158 | error!("Keyword {} is reserved", ident); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:158:13 [INFO] [stdout] | [INFO] [stdout] 158 | error!("Keyword {} is reserved", ident); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:158:13 [INFO] [stdout] | [INFO] [stdout] 158 | error!("Keyword {} is reserved", ident); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:158:13 [INFO] [stdout] | [INFO] [stdout] 158 | error!("Keyword {} is reserved", ident); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:158:13 [INFO] [stdout] | [INFO] [stdout] 158 | error!("Keyword {} is reserved", ident); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:618:17 [INFO] [stdout] | [INFO] [stdout] 618 | error!("Error in lambda declaration: invalid form for args (must be a list of idents"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:618:17 [INFO] [stdout] | [INFO] [stdout] 618 | error!("Error in lambda declaration: invalid form for args (must be a list of idents"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:618:17 [INFO] [stdout] | [INFO] [stdout] 618 | error!("Error in lambda declaration: invalid form for args (must be a list of idents"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:618:17 [INFO] [stdout] | [INFO] [stdout] 618 | error!("Error in lambda declaration: invalid form for args (must be a list of idents"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:618:17 [INFO] [stdout] | [INFO] [stdout] 618 | error!("Error in lambda declaration: invalid form for args (must be a list of idents"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:648:49 [INFO] [stdout] | [INFO] [stdout] 648 | ... error!("Error in, lambda for name, expected ident, got {:?}", a); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:648:49 [INFO] [stdout] | [INFO] [stdout] 648 | ... error!("Error in, lambda for name, expected ident, got {:?}", a); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:648:49 [INFO] [stdout] | [INFO] [stdout] 648 | ... error!("Error in, lambda for name, expected ident, got {:?}", a); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:648:49 [INFO] [stdout] | [INFO] [stdout] 648 | ... error!("Error in, lambda for name, expected ident, got {:?}", a); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:648:49 [INFO] [stdout] | [INFO] [stdout] 648 | ... error!("Error in, lambda for name, expected ident, got {:?}", a); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:686:25 [INFO] [stdout] | [INFO] [stdout] 686 | error!("Lambda depends on ident {} but it can't be found in this context", &k); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:686:25 [INFO] [stdout] | [INFO] [stdout] 686 | error!("Lambda depends on ident {} but it can't be found in this context", &k); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:686:25 [INFO] [stdout] | [INFO] [stdout] 686 | error!("Lambda depends on ident {} but it can't be found in this context", &k); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:686:25 [INFO] [stdout] | [INFO] [stdout] 686 | error!("Lambda depends on ident {} but it can't be found in this context", &k); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:686:25 [INFO] [stdout] | [INFO] [stdout] 686 | error!("Lambda depends on ident {} but it can't be found in this context", &k); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:736:17 [INFO] [stdout] | [INFO] [stdout] 736 | info!("{:?}", a1); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:736:17 [INFO] [stdout] | [INFO] [stdout] 736 | info!("{:?}", a1); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:736:17 [INFO] [stdout] | [INFO] [stdout] 736 | info!("{:?}", a1); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:736:17 [INFO] [stdout] | [INFO] [stdout] 736 | info!("{:?}", a1); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:736:17 [INFO] [stdout] | [INFO] [stdout] 736 | info!("{:?}", a1); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:750:53 [INFO] [stdout] | [INFO] [stdout] 750 | ... info!("args: {:?}", args); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:750:53 [INFO] [stdout] | [INFO] [stdout] 750 | ... info!("args: {:?}", args); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:750:53 [INFO] [stdout] | [INFO] [stdout] 750 | ... info!("args: {:?}", args); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:750:53 [INFO] [stdout] | [INFO] [stdout] 750 | ... info!("args: {:?}", args); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:750:53 [INFO] [stdout] | [INFO] [stdout] 750 | ... info!("args: {:?}", args); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:751:53 [INFO] [stdout] | [INFO] [stdout] 751 | ... info!("evalued {} to {:?}", s, v); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:751:53 [INFO] [stdout] | [INFO] [stdout] 751 | ... info!("evalued {} to {:?}", s, v); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:751:53 [INFO] [stdout] | [INFO] [stdout] 751 | ... info!("evalued {} to {:?}", s, v); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:751:53 [INFO] [stdout] | [INFO] [stdout] 751 | ... info!("evalued {} to {:?}", s, v); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:751:53 [INFO] [stdout] | [INFO] [stdout] 751 | ... info!("evalued {} to {:?}", s, v); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:767:33 [INFO] [stdout] | [INFO] [stdout] 767 | ... info!("evalued {} to {:?}", s, v); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:767:33 [INFO] [stdout] | [INFO] [stdout] 767 | ... info!("evalued {} to {:?}", s, v); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:767:33 [INFO] [stdout] | [INFO] [stdout] 767 | ... info!("evalued {} to {:?}", s, v); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:767:33 [INFO] [stdout] | [INFO] [stdout] 767 | ... info!("evalued {} to {:?}", s, v); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:767:33 [INFO] [stdout] | [INFO] [stdout] 767 | ... info!("evalued {} to {:?}", s, v); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:791:13 [INFO] [stdout] | [INFO] [stdout] 791 | info!("Debug: macroexpand gives\n{}", res.expr.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:791:13 [INFO] [stdout] | [INFO] [stdout] 791 | info!("Debug: macroexpand gives\n{}", res.expr.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:791:13 [INFO] [stdout] | [INFO] [stdout] 791 | info!("Debug: macroexpand gives\n{}", res.expr.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:791:13 [INFO] [stdout] | [INFO] [stdout] 791 | info!("Debug: macroexpand gives\n{}", res.expr.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/eval.rs:791:13 [INFO] [stdout] | [INFO] [stdout] 791 | info!("Debug: macroexpand gives\n{}", res.expr.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead [INFO] [stdout] --> src/expr.rs:33:13 [INFO] [stdout] | [INFO] [stdout] 33 | try!(formatter.write_str(" ")); [INFO] [stdout] | ^^^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(deprecated)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead [INFO] [stdout] --> src/expr.rs:34:13 [INFO] [stdout] | [INFO] [stdout] 34 | try!(e1.fmt(formatter)); [INFO] [stdout] | ^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead [INFO] [stdout] --> src/expr.rs:54:17 [INFO] [stdout] | [INFO] [stdout] 54 | try!(formatter.write_str("'")); [INFO] [stdout] | ^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead [INFO] [stdout] --> src/expr.rs:58:17 [INFO] [stdout] | [INFO] [stdout] 58 | try!(formatter.write_str("(")); [INFO] [stdout] | ^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead [INFO] [stdout] --> src/expr.rs:59:17 [INFO] [stdout] | [INFO] [stdout] 59 | try!(e1.fmt(formatter)); [INFO] [stdout] | ^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead [INFO] [stdout] --> src/expr.rs:63:17 [INFO] [stdout] | [INFO] [stdout] 63 | try!(formatter.write_str(",")); [INFO] [stdout] | ^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead [INFO] [stdout] --> src/expr.rs:67:17 [INFO] [stdout] | [INFO] [stdout] 67 | try!(formatter.write_str("`")); [INFO] [stdout] | ^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:43:17 [INFO] [stdout] | [INFO] [stdout] 43 | error!("Error flushing stdout. abort"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:43:17 [INFO] [stdout] | [INFO] [stdout] 43 | error!("Error flushing stdout. abort"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:43:17 [INFO] [stdout] | [INFO] [stdout] 43 | error!("Error flushing stdout. abort"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:43:17 [INFO] [stdout] | [INFO] [stdout] 43 | error!("Error flushing stdout. abort"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:43:17 [INFO] [stdout] | [INFO] [stdout] 43 | error!("Error flushing stdout. abort"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:68:21 [INFO] [stdout] | [INFO] [stdout] 68 | info!("{:?}", c.env) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:68:21 [INFO] [stdout] | [INFO] [stdout] 68 | info!("{:?}", c.env) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:68:21 [INFO] [stdout] | [INFO] [stdout] 68 | info!("{:?}", c.env) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:68:21 [INFO] [stdout] | [INFO] [stdout] 68 | info!("{:?}", c.env) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:68:21 [INFO] [stdout] | [INFO] [stdout] 68 | info!("{:?}", c.env) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: variable does not need to be mutable [INFO] [stdout] --> src/eval.rs:438:13 [INFO] [stdout] | [INFO] [stdout] 438 | let mut new_c:Context; [INFO] [stdout] | ----^^^^^ [INFO] [stdout] | | [INFO] [stdout] | help: remove this `mut` [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(unused_mut)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: internal compiler error: compiler/rustc_mir_build/src/builder/scope.rs:1724:17: cannot unwind from goto -> bb289 [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] thread 'rustc' panicked at compiler/rustc_mir_build/src/builder/scope.rs:1724:17: [INFO] [stderr] Box [INFO] [stderr] stack backtrace: [INFO] [stderr] 0: 0x7fa3afd81caa - ::fmt::h636462e57d5ef1e1 [INFO] [stderr] 1: 0x7fa3b0413cbc - core::fmt::write::h067060808ac50eb9 [INFO] [stderr] 2: 0x7fa3b1328e11 - std::io::Write::write_fmt::h4674fa2ed7c0dfdd [INFO] [stderr] 3: 0x7fa3afd81b02 - std::sys::backtrace::BacktraceLock::print::h0c77148acfb0b5e9 [INFO] [stderr] 4: 0x7fa3afd83ffa - std::panicking::default_hook::{{closure}}::h30daa8e7c6ccb09d [INFO] [stderr] 5: 0x7fa3afd83e43 - std::panicking::default_hook::h25f21dc0f2064615 [INFO] [stderr] 6: 0x7fa3aeeeff28 - std[b36e883d67eb0403]::panicking::update_hook::>::{closure#0} [INFO] [stderr] 7: 0x7fa3afd847b8 - std::panicking::rust_panic_with_hook::hc98438687e833605 [INFO] [stderr] 8: 0x7fa3aef2a341 - std[b36e883d67eb0403]::panicking::begin_panic::::{closure#0} [INFO] [stderr] 9: 0x7fa3aef1f526 - std[b36e883d67eb0403]::sys::backtrace::__rust_end_short_backtrace::::{closure#0}, !> [INFO] [stderr] 10: 0x7fa3aef1f50d - std[b36e883d67eb0403]::panicking::begin_panic:: [INFO] [stderr] 11: 0x7fa3aef342a1 - ::emit_producing_guarantee [INFO] [stderr] 12: 0x7fa3af484fdc - ::span_bug:: [INFO] [stderr] 13: 0x7fa3af50a897 - rustc_middle[8ad6e8ce52578819]::util::bug::opt_span_bug_fmt::::{closure#0} [INFO] [stderr] 14: 0x7fa3af4f006a - rustc_middle[8ad6e8ce52578819]::ty::context::tls::with_opt::::{closure#0}, !>::{closure#0} [INFO] [stderr] 15: 0x7fa3af4efefb - rustc_middle[8ad6e8ce52578819]::ty::context::tls::with_context_opt::::{closure#0}, !>::{closure#0}, !> [INFO] [stderr] 16: 0x7fa3ad934437 - rustc_middle[8ad6e8ce52578819]::util::bug::span_bug_fmt:: [INFO] [stderr] 17: 0x7fa3b0dd541b - ::build_unwind_tree [INFO] [stderr] 18: 0x7fa3b0dcd7cd - rustc_mir_build[73684a27b88b946a]::builder::mir_build [INFO] [stderr] 19: 0x7fa3b0407714 - rustc_mir_transform[857cd804783fef4d]::mir_built [INFO] [stderr] 20: 0x7fa3b04076d7 - rustc_query_impl[1e55094a59e290f4]::plumbing::__rust_begin_short_backtrace::> [INFO] [stderr] 21: 0x7fa3b06953d1 - rustc_query_system[67781f9dc633c543]::query::plumbing::try_execute_query::, rustc_query_system[67781f9dc633c543]::dep_graph::graph::DepNodeIndex>, false, false, false>, rustc_query_impl[1e55094a59e290f4]::plumbing::QueryCtxt, false> [INFO] [stderr] 22: 0x7fa3b0694f8d - rustc_query_impl[1e55094a59e290f4]::query_impl::mir_built::get_query_non_incr::__rust_end_short_backtrace [INFO] [stderr] 23: 0x7fa3ad467185 - rustc_mir_build[73684a27b88b946a]::check_unsafety::check_unsafety [INFO] [stderr] 24: 0x7fa3b0ce98a7 - rustc_query_impl[1e55094a59e290f4]::plumbing::__rust_begin_short_backtrace::> [INFO] [stderr] 25: 0x7fa3b0ce9b69 - rustc_query_system[67781f9dc633c543]::query::plumbing::try_execute_query::, rustc_query_system[67781f9dc633c543]::dep_graph::graph::DepNodeIndex>, false, false, false>, rustc_query_impl[1e55094a59e290f4]::plumbing::QueryCtxt, false> [INFO] [stderr] 26: 0x7fa3b0ce97d1 - rustc_query_impl[1e55094a59e290f4]::query_impl::check_unsafety::get_query_non_incr::__rust_end_short_backtrace [INFO] [stderr] 27: 0x7fa3b089bd32 - rustc_interface[b59e7ee7606ca029]::passes::run_required_analyses [INFO] [stderr] 28: 0x7fa3b132cc9e - rustc_interface[b59e7ee7606ca029]::passes::analysis [INFO] [stderr] 29: 0x7fa3b132cc6f - rustc_query_impl[1e55094a59e290f4]::plumbing::__rust_begin_short_backtrace::> [INFO] [stderr] 30: 0x7fa3b137b355 - rustc_query_system[67781f9dc633c543]::query::plumbing::try_execute_query::>, false, false, false>, rustc_query_impl[1e55094a59e290f4]::plumbing::QueryCtxt, false> [INFO] [stderr] 31: 0x7fa3b137b08e - rustc_query_impl[1e55094a59e290f4]::query_impl::analysis::get_query_non_incr::__rust_end_short_backtrace [INFO] [stderr] 32: 0x7fa3b13701de - rustc_interface[b59e7ee7606ca029]::passes::create_and_enter_global_ctxt::, rustc_driver_impl[be5855d19ccc8b6c]::run_compiler::{closure#0}::{closure#2}>::{closure#2}::{closure#0} [INFO] [stderr] 33: 0x7fa3b13dff51 - rustc_interface[b59e7ee7606ca029]::interface::run_compiler::<(), rustc_driver_impl[be5855d19ccc8b6c]::run_compiler::{closure#0}>::{closure#1} [INFO] [stderr] 34: 0x7fa3b12f5087 - std[b36e883d67eb0403]::sys::backtrace::__rust_begin_short_backtrace::::{closure#1}, ()>::{closure#0}, ()>::{closure#0}::{closure#0}, ()> [INFO] [stderr] 35: 0x7fa3b12f551c - <::spawn_unchecked_::{closure#1}, ()>::{closure#0}, ()>::{closure#0}::{closure#0}, ()>::{closure#1} as core[303105738bd0c2ae]::ops::function::FnOnce<()>>::call_once::{shim:vtable#0} [INFO] [stderr] 36: 0x7fa3b12f6aef - std::sys::pal::unix::thread::Thread::new::thread_start::ha554cc4ba6335b05 [INFO] [stderr] 37: 0x7fa3b2a3bac3 - [INFO] [stderr] 38: 0x7fa3b2acca04 - clone [INFO] [stderr] 39: 0x0 - [INFO] [stderr] [INFO] [stderr] note: we would appreciate a bug report: https://github.com/rust-lang/rust/issues/new?labels=C-bug%2C+I-ICE%2C+T-compiler&template=ice.md [INFO] [stderr] [INFO] [stderr] note: please make sure that you have updated to the latest nightly [INFO] [stderr] [INFO] [stderr] warning: the ICE couldn't be written to `/opt/rustwide/workdir/rustc-ice-2025-01-01T01_08_53-23.txt`: Read-only file system (os error 30) [INFO] [stderr] [INFO] [stderr] note: rustc 1.85.0-nightly (9b5e8b16b 2024-12-19) running on x86_64-unknown-linux-gnu [INFO] [stderr] [INFO] [stderr] note: compiler flags: --crate-type bin -C embed-bitcode=no -C debuginfo=2 [INFO] [stderr] [INFO] [stderr] note: some of the compiler flags provided by cargo are hidden [INFO] [stderr] [INFO] [stderr] query stack during panic: [INFO] [stderr] #0 [mir_built] building MIR for `eval::::eval_lambda` [INFO] [stdout] error: internal compiler error: compiler/rustc_mir_build/src/builder/scope.rs:1724:17: cannot unwind from goto -> bb303 [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] #1 [check_unsafety] unsafety-checking `eval::::eval_lambda` [INFO] [stderr] #2 [analysis] running analysis passes on this crate [INFO] [stderr] end of query stack [INFO] [stderr] thread 'rustc' panicked at compiler/rustc_mir_build/src/builder/scope.rs:1724:17: [INFO] [stderr] Box [INFO] [stderr] stack backtrace: [INFO] [stderr] 0: 0x7fa3afd81caa - ::fmt::h636462e57d5ef1e1 [INFO] [stderr] 1: 0x7fa3b0413cbc - core::fmt::write::h067060808ac50eb9 [INFO] [stderr] 2: 0x7fa3b1328e11 - std::io::Write::write_fmt::h4674fa2ed7c0dfdd [INFO] [stderr] 3: 0x7fa3afd81b02 - std::sys::backtrace::BacktraceLock::print::h0c77148acfb0b5e9 [INFO] [stderr] 4: 0x7fa3afd83ffa - std::panicking::default_hook::{{closure}}::h30daa8e7c6ccb09d [INFO] [stderr] 5: 0x7fa3afd83e43 - std::panicking::default_hook::h25f21dc0f2064615 [INFO] [stderr] 6: 0x7fa3aeeeff28 - std[b36e883d67eb0403]::panicking::update_hook::>::{closure#0} [INFO] [stderr] 7: 0x7fa3afd847b8 - std::panicking::rust_panic_with_hook::hc98438687e833605 [INFO] [stderr] 8: 0x7fa3aef2a341 - std[b36e883d67eb0403]::panicking::begin_panic::::{closure#0} [INFO] [stderr] 9: 0x7fa3aef1f526 - std[b36e883d67eb0403]::sys::backtrace::__rust_end_short_backtrace::::{closure#0}, !> [INFO] [stderr] 10: 0x7fa3aef1f50d - std[b36e883d67eb0403]::panicking::begin_panic:: [INFO] [stderr] 11: 0x7fa3aef342a1 - ::emit_producing_guarantee [INFO] [stderr] 12: 0x7fa3af484fdc - ::span_bug:: [INFO] [stderr] 13: 0x7fa3af50a897 - rustc_middle[8ad6e8ce52578819]::util::bug::opt_span_bug_fmt::::{closure#0} [INFO] [stderr] 14: 0x7fa3af4f006a - rustc_middle[8ad6e8ce52578819]::ty::context::tls::with_opt::::{closure#0}, !>::{closure#0} [INFO] [stderr] 15: 0x7fa3af4efefb - rustc_middle[8ad6e8ce52578819]::ty::context::tls::with_context_opt::::{closure#0}, !>::{closure#0}, !> [INFO] [stderr] 16: 0x7fa3ad934437 - rustc_middle[8ad6e8ce52578819]::util::bug::span_bug_fmt:: [INFO] [stderr] 17: 0x7fa3b0dd541b - ::build_unwind_tree [INFO] [stderr] 18: 0x7fa3b0dcd7cd - rustc_mir_build[73684a27b88b946a]::builder::mir_build [INFO] [stderr] 19: 0x7fa3b0407714 - rustc_mir_transform[857cd804783fef4d]::mir_built [INFO] [stderr] 20: 0x7fa3b04076d7 - rustc_query_impl[1e55094a59e290f4]::plumbing::__rust_begin_short_backtrace::> [INFO] [stderr] 21: 0x7fa3b06953d1 - rustc_query_system[67781f9dc633c543]::query::plumbing::try_execute_query::, rustc_query_system[67781f9dc633c543]::dep_graph::graph::DepNodeIndex>, false, false, false>, rustc_query_impl[1e55094a59e290f4]::plumbing::QueryCtxt, false> [INFO] [stderr] 22: 0x7fa3b0694f8d - rustc_query_impl[1e55094a59e290f4]::query_impl::mir_built::get_query_non_incr::__rust_end_short_backtrace [INFO] [stderr] 23: 0x7fa3ad467185 - rustc_mir_build[73684a27b88b946a]::check_unsafety::check_unsafety [INFO] [stderr] 24: 0x7fa3b0ce98a7 - rustc_query_impl[1e55094a59e290f4]::plumbing::__rust_begin_short_backtrace::> [INFO] [stderr] 25: 0x7fa3b0ce9b69 - rustc_query_system[67781f9dc633c543]::query::plumbing::try_execute_query::, rustc_query_system[67781f9dc633c543]::dep_graph::graph::DepNodeIndex>, false, false, false>, rustc_query_impl[1e55094a59e290f4]::plumbing::QueryCtxt, false> [INFO] [stderr] 26: 0x7fa3b0ce97d1 - rustc_query_impl[1e55094a59e290f4]::query_impl::check_unsafety::get_query_non_incr::__rust_end_short_backtrace [INFO] [stderr] 27: 0x7fa3b089bd32 - rustc_interface[b59e7ee7606ca029]::passes::run_required_analyses [INFO] [stderr] 28: 0x7fa3b132cc9e - rustc_interface[b59e7ee7606ca029]::passes::analysis [INFO] [stderr] 29: 0x7fa3b132cc6f - rustc_query_impl[1e55094a59e290f4]::plumbing::__rust_begin_short_backtrace::> [INFO] [stderr] 30: 0x7fa3b137b355 - rustc_query_system[67781f9dc633c543]::query::plumbing::try_execute_query::>, false, false, false>, rustc_query_impl[1e55094a59e290f4]::plumbing::QueryCtxt, false> [INFO] [stderr] 31: 0x7fa3b137b08e - rustc_query_impl[1e55094a59e290f4]::query_impl::analysis::get_query_non_incr::__rust_end_short_backtrace [INFO] [stderr] 32: 0x7fa3b13701de - rustc_interface[b59e7ee7606ca029]::passes::create_and_enter_global_ctxt::, rustc_driver_impl[be5855d19ccc8b6c]::run_compiler::{closure#0}::{closure#2}>::{closure#2}::{closure#0} [INFO] [stderr] 33: 0x7fa3b13dff51 - rustc_interface[b59e7ee7606ca029]::interface::run_compiler::<(), rustc_driver_impl[be5855d19ccc8b6c]::run_compiler::{closure#0}>::{closure#1} [INFO] [stderr] 34: 0x7fa3b12f5087 - std[b36e883d67eb0403]::sys::backtrace::__rust_begin_short_backtrace::::{closure#1}, ()>::{closure#0}, ()>::{closure#0}::{closure#0}, ()> [INFO] [stderr] 35: 0x7fa3b12f551c - <::spawn_unchecked_::{closure#1}, ()>::{closure#0}, ()>::{closure#0}::{closure#0}, ()>::{closure#1} as core[303105738bd0c2ae]::ops::function::FnOnce<()>>::call_once::{shim:vtable#0} [INFO] [stderr] 36: 0x7fa3b12f6aef - std::sys::pal::unix::thread::Thread::new::thread_start::ha554cc4ba6335b05 [INFO] [stderr] 37: 0x7fa3b2a3bac3 - [INFO] [stderr] 38: 0x7fa3b2acca04 - clone [INFO] [stderr] 39: 0x0 - [INFO] [stderr] [INFO] [stderr] note: we would appreciate a bug report: https://github.com/rust-lang/rust/issues/new?labels=C-bug%2C+I-ICE%2C+T-compiler&template=ice.md [INFO] [stderr] [INFO] [stderr] note: please make sure that you have updated to the latest nightly [INFO] [stderr] [INFO] [stderr] warning: the ICE couldn't be written to `/opt/rustwide/workdir/rustc-ice-2025-01-01T01_08_53-23.txt`: Read-only file system (os error 30) [INFO] [stderr] [INFO] [stderr] note: rustc 1.85.0-nightly (9b5e8b16b 2024-12-19) running on x86_64-unknown-linux-gnu [INFO] [stderr] [INFO] [stderr] note: compiler flags: --crate-type bin -C embed-bitcode=no -C debuginfo=2 [INFO] [stderr] [INFO] [stderr] note: some of the compiler flags provided by cargo are hidden [INFO] [stderr] [INFO] [stderr] query stack during panic: [INFO] [stderr] #0 [mir_built] building MIR for `eval::::eval_fn_args` [INFO] [stderr] #1 [check_unsafety] unsafety-checking `eval::::eval_fn_args` [INFO] [stderr] #2 [analysis] running analysis passes on this crate [INFO] [stderr] end of query stack [INFO] [stderr] error: could not compile `rscheme` (bin "rscheme"); 152 warnings emitted [INFO] [stderr] [INFO] [stderr] Caused by: [INFO] [stderr] process didn't exit successfully: `/opt/rustwide/rustup-home/toolchains/9b5e8b16bd1c4acf4cf8e6880368314cf021a987/bin/rustc --crate-name rscheme --edition=2015 src/main.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C debuginfo=2 --check-cfg 'cfg(docsrs)' --check-cfg 'cfg(feature, values())' -C metadata=39bd6b3ac71238ee -C extra-filename=-506173325966fd6a --out-dir /opt/rustwide/target/debug/deps -L dependency=/opt/rustwide/target/debug/deps --extern log=/opt/rustwide/target/debug/deps/liblog-c2d283bbad01f5f5.rlib --cap-lints=forbid -Dtail-expr-drop-order` (exit status: 101) [INFO] running `Command { std: "docker" "inspect" "2eec89ea83a730ec251abd46cb2e4b9df41afed426f292bccdd775e1215421e1", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "2eec89ea83a730ec251abd46cb2e4b9df41afed426f292bccdd775e1215421e1", kill_on_drop: false }` [INFO] [stdout] 2eec89ea83a730ec251abd46cb2e4b9df41afed426f292bccdd775e1215421e1