[INFO] fetching crate koto_runtime 0.12.0...
[INFO] checking koto_runtime-0.12.0 against nightly-2024-02-05 for check-cfg
[INFO] extracting crate koto_runtime 0.12.0 into /workspace/builds/worker-0-tc1/source
[INFO] validating manifest of crates.io crate koto_runtime 0.12.0 on toolchain nightly-2024-02-05
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+nightly-2024-02-05" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] started tweaking crates.io crate koto_runtime 0.12.0
[INFO] finished tweaking crates.io crate koto_runtime 0.12.0
[INFO] tweaked toml for crates.io crate koto_runtime 0.12.0 written to /workspace/builds/worker-0-tc1/source/Cargo.toml
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+nightly-2024-02-05" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Updating crates.io index
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+nightly-2024-02-05" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]  Downloading crates ...
[INFO] [stderr]   Downloaded koto_lexer v0.12.0
[INFO] [stderr]   Downloaded koto_memory v0.12.0
[INFO] [stderr]   Downloaded koto_bytecode v0.12.0
[INFO] [stderr]   Downloaded koto_parser v0.12.0
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:2788e3201cd34a07e3172128adcd8b3090168a8e3bcc40d7c032b9dda1df7d1c" "/opt/rustwide/cargo-home/bin/cargo" "+nightly-2024-02-05" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] 6b74a47faa49064d5544608058041cd034064fa9a6ec42f67b7b0753a2d4148e
[INFO] running `Command { std: "docker" "start" "-a" "6b74a47faa49064d5544608058041cd034064fa9a6ec42f67b7b0753a2d4148e", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "6b74a47faa49064d5544608058041cd034064fa9a6ec42f67b7b0753a2d4148e", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "6b74a47faa49064d5544608058041cd034064fa9a6ec42f67b7b0753a2d4148e", kill_on_drop: false }`
[INFO] [stdout] 6b74a47faa49064d5544608058041cd034064fa9a6ec42f67b7b0753a2d4148e
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:2788e3201cd34a07e3172128adcd8b3090168a8e3bcc40d7c032b9dda1df7d1c" "/opt/rustwide/cargo-home/bin/cargo" "+nightly-2024-02-05" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] 6e231036c904239bd2cd22fd4f3a5f76d40192b6bfba10594134bca5bd862068
[INFO] running `Command { std: "docker" "start" "-a" "6e231036c904239bd2cd22fd4f3a5f76d40192b6bfba10594134bca5bd862068", kill_on_drop: false }`
[INFO] [stderr]     Checking koto_memory v0.12.0
[INFO] [stderr]    Compiling num-traits v0.2.17
[INFO] [stderr]     Checking koto_lexer v0.12.0
[INFO] [stderr]     Checking iana-time-zone v0.1.60
[INFO] [stderr]     Checking dunce v1.0.4
[INFO] [stderr]     Checking smallvec v1.13.1
[INFO] [stderr]     Checking instant v0.1.12
[INFO] [stderr]     Checking koto_parser v0.12.0
[INFO] [stderr]     Checking koto_bytecode v0.12.0
[INFO] [stderr]     Checking chrono v0.4.33
[INFO] [stderr]     Checking koto_runtime v0.12.0 (/opt/rustwide/workdir)
[INFO] [stdout] warning: use of deprecated method `indexmap::IndexMap::<K, V, S>::remove`: `remove` disrupts the map order -- use `swap_remove` or `shift_remove` for explicit behavior.
[INFO] [stdout]    --> src/types/map.rs:237:39
[INFO] [stdout]     |
[INFO] [stdout] 237 |         assert!(matches!(m.data_mut().remove("test"), Some(Value::Null)));
[INFO] [stdout]     |                                       ^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: `#[warn(deprecated)]` on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: 1 warning emitted
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 4.55s
[INFO] running `Command { std: "docker" "inspect" "6e231036c904239bd2cd22fd4f3a5f76d40192b6bfba10594134bca5bd862068", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "6e231036c904239bd2cd22fd4f3a5f76d40192b6bfba10594134bca5bd862068", kill_on_drop: false }`
[INFO] [stdout] 6e231036c904239bd2cd22fd4f3a5f76d40192b6bfba10594134bca5bd862068
[INFO] checking koto_runtime-0.12.0 against nightly-2024-02-05+rustflags=-Dunexpected_cfgs+cargoflags=-Zcheck-cfg for check-cfg
[INFO] extracting crate koto_runtime 0.12.0 into /workspace/builds/worker-0-tc2/source
[INFO] validating manifest of crates.io crate koto_runtime 0.12.0 on toolchain nightly-2024-02-05
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+nightly-2024-02-05" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] started tweaking crates.io crate koto_runtime 0.12.0
[INFO] finished tweaking crates.io crate koto_runtime 0.12.0
[INFO] tweaked toml for crates.io crate koto_runtime 0.12.0 written to /workspace/builds/worker-0-tc2/source/Cargo.toml
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+nightly-2024-02-05" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Updating crates.io index
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+nightly-2024-02-05" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-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:2788e3201cd34a07e3172128adcd8b3090168a8e3bcc40d7c032b9dda1df7d1c" "/opt/rustwide/cargo-home/bin/cargo" "+nightly-2024-02-05" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] 074747479d492759271bcfae325f523115d88314d0ce433970477595e4ae9e43
[INFO] running `Command { std: "docker" "start" "-a" "074747479d492759271bcfae325f523115d88314d0ce433970477595e4ae9e43", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "074747479d492759271bcfae325f523115d88314d0ce433970477595e4ae9e43", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "074747479d492759271bcfae325f523115d88314d0ce433970477595e4ae9e43", kill_on_drop: false }`
[INFO] [stdout] 074747479d492759271bcfae325f523115d88314d0ce433970477595e4ae9e43
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-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 -Dunexpected_cfgs" "-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:2788e3201cd34a07e3172128adcd8b3090168a8e3bcc40d7c032b9dda1df7d1c" "/opt/rustwide/cargo-home/bin/cargo" "+nightly-2024-02-05" "check" "--frozen" "--all" "--all-targets" "--message-format=json" "-Zcheck-cfg", kill_on_drop: false }`
[INFO] [stdout] 4bccff5c4d3b1458772941f4a7e35099f4e0e37987425308e9b9613930dd8665
[INFO] running `Command { std: "docker" "start" "-a" "4bccff5c4d3b1458772941f4a7e35099f4e0e37987425308e9b9613930dd8665", kill_on_drop: false }`
[INFO] [stderr]     Checking koto_memory v0.12.0
[INFO] [stderr]     Checking smallvec v1.13.1
[INFO] [stderr]    Compiling num-traits v0.2.17
[INFO] [stderr]     Checking koto_lexer v0.12.0
[INFO] [stderr]     Checking dunce v1.0.4
[INFO] [stderr]     Checking iana-time-zone v0.1.60
[INFO] [stderr]     Checking instant v0.1.12
[INFO] [stderr]     Checking koto_parser v0.12.0
[INFO] [stderr]     Checking koto_bytecode v0.12.0
[INFO] [stderr]     Checking chrono v0.4.33
[INFO] [stderr]     Checking koto_runtime v0.12.0 (/opt/rustwide/workdir)
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 192 | /     runtime_error!(ErrorKind::UnexpectedType {
[INFO] [stdout] 193 | |         expected: expected_str.into(),
[INFO] [stdout] 194 | |         unexpected: unexpected.into(),
[INFO] [stdout] 195 | |     })
[INFO] [stdout]     | |______- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: expected names are: `debug_assertions`, `doc`, `doctest`, `feature`, `miri`, `overflow_checks`, `panic`, `proc_macro`, `relocation_model`, `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`, `unix`, `windows`
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: requested on the command line with `-D unexpected-cfgs`
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/io/file.rs:10:9
[INFO] [stdout]     |
[INFO] [stdout] 10  |         runtime_error!("unsupported for this file type")
[INFO] [stdout]     |         ------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/io/file.rs:15:9
[INFO] [stdout]     |
[INFO] [stdout] 15  |         runtime_error!("unsupported for this file type")
[INFO] [stdout]     |         ------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/io/file.rs:25:9
[INFO] [stdout]     |
[INFO] [stdout] 25  |         runtime_error!("unsupported for this file type")
[INFO] [stdout]     |         ------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/io/file.rs:30:9
[INFO] [stdout]     |
[INFO] [stdout] 30  |         runtime_error!("unsupported for this file type")
[INFO] [stdout]     |         ------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/io/file.rs:38:9
[INFO] [stdout]     |
[INFO] [stdout] 38  |         runtime_error!("unsupported for this file type")
[INFO] [stdout]     |         ------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/io/file.rs:43:9
[INFO] [stdout]     |
[INFO] [stdout] 43  |         runtime_error!("unsupported for this file type")
[INFO] [stdout]     |         ------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/io/file.rs:48:9
[INFO] [stdout]     |
[INFO] [stdout] 48  |         runtime_error!("unsupported for this file type")
[INFO] [stdout]     |         ------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/types/iterator.rs:196:13
[INFO] [stdout]     |
[INFO] [stdout] 196 |             runtime_error!("Unbounded ranges can't be used as iterators (range: {range})")
[INFO] [stdout]     |             ------------------------------------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/types/iterator.rs:411:28
[INFO] [stdout]     |
[INFO] [stdout] 411 |             None => return runtime_error!("Expected implementation of @next"),
[INFO] [stdout]     |                            -------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/types/iterator.rs:477:13
[INFO] [stdout]     |
[INFO] [stdout] 477 |             runtime_error!("{} is not an iterator", object.try_borrow()?.object_type())
[INFO] [stdout]     |             --------------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/types/map.rs:185:32
[INFO] [stdout]     |
[INFO] [stdout] 185 |                 .ok_or_else(|| make_runtime_error!("Missing VM in map display op"))?
[INFO] [stdout]     |                                --------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `make_runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/types/meta_map.rs:247:32
[INFO] [stdout]     |
[INFO] [stdout] 247 |             name.ok_or_else(|| make_runtime_error!("Missing name for named meta entry"))?,
[INFO] [stdout]     |                                -------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `make_runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/types/meta_map.rs:251:46
[INFO] [stdout]     |
[INFO] [stdout] 251 |             MetaKey::Test(name.ok_or_else(|| make_runtime_error!("Missing name for test"))?)
[INFO] [stdout]     |                                              -------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `make_runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/types/meta_map.rs:258:38
[INFO] [stdout]     |
[INFO] [stdout] 258 |         MetaKeyId::Invalid => return runtime_error!("Invalid MetaKeyId"),
[INFO] [stdout]     |                                      ----------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/types/object.rs:236:13
[INFO] [stdout]     |
[INFO] [stdout] 236 |             make_runtime_error!("Attempting to borrow an object that is already mutably borrowed")
[INFO] [stdout]     |             -------------------------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `make_runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/types/object.rs:243:13
[INFO] [stdout]     |
[INFO] [stdout] 243 |             make_runtime_error!("Attempting to borrow an object that is already mutably borrowed")
[INFO] [stdout]     |             -------------------------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `make_runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/types/object.rs:250:26
[INFO] [stdout]     |
[INFO] [stdout] 250 |             .map_err(|_| make_runtime_error!("Incorrect object type"))
[INFO] [stdout]     |                          -------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `make_runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/types/object.rs:256:26
[INFO] [stdout]     |
[INFO] [stdout] 256 |             .map_err(|_| make_runtime_error!("Incorrect object type"))
[INFO] [stdout]     |                          -------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `make_runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/types/object.rs:453:5
[INFO] [stdout]     |
[INFO] [stdout] 453 |     runtime_error!("{method} is unimplemented for {object_type}")
[INFO] [stdout]     |     ------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/types/range.rs:260:25
[INFO] [stdout]     |
[INFO] [stdout] 260 |             _ => return runtime_error!("KRange::pop_front can only be used with bounded ranges"),
[INFO] [stdout]     |                         ------------------------------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/types/range.rs:325:25
[INFO] [stdout]     |
[INFO] [stdout] 325 |             _ => return runtime_error!("KRange::pop_back can only be used with bounded ranges"),
[INFO] [stdout]     |                         ----------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/types/value.rs:238:13
[INFO] [stdout]     |
[INFO] [stdout] 238 |             runtime_error!("Failed to write to string")
[INFO] [stdout]     |             ------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/types/value_key.rs:29:13
[INFO] [stdout]     |
[INFO] [stdout] 29  |             runtime_error!("Only hashable values can be used as value keys")
[INFO] [stdout]     |             ---------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/vm.rs:278:20
[INFO] [stdout]     |
[INFO] [stdout] 278 |             return runtime_error!("run_function: the provided value isn't a function");
[INFO] [stdout]     |                    ------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/vm.rs:531:36
[INFO] [stdout]     |
[INFO] [stdout] 531 |                     NotIterable => runtime_error!("{} is not iterable", o_inner.object_type()),
[INFO] [stdout]     |                                    ----------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/vm.rs:539:17
[INFO] [stdout]     |
[INFO] [stdout] 539 | /                 runtime_error!(
[INFO] [stdout] 540 | |                     "expected iterable value, found '{}'",
[INFO] [stdout] 541 | |                     unexpected.type_as_string(),
[INFO] [stdout] 542 | |                 )
[INFO] [stdout]     | |_________________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/vm.rs:689:34
[INFO] [stdout]     |
[INFO] [stdout] 689 |             Error { message } => runtime_error!(message)?,
[INFO] [stdout]     |                                  ----------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/vm.rs:952:13
[INFO] [stdout]     |
[INFO] [stdout] 952 |             runtime_error!("'{name}' not found")
[INFO] [stdout]     |             ------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:1049:32
[INFO] [stdout]      |
[INFO] [stdout] 1049 |                         return runtime_error!("{} is not iterable", o_inner.object_type())
[INFO] [stdout]      |                                ----------------------------------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:1098:32
[INFO] [stdout]      |
[INFO] [stdout] 1098 |                         return runtime_error!(error.to_string());
[INFO] [stdout]      |                                --------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:1298:20
[INFO] [stdout]      |
[INFO] [stdout] 1298 |             return runtime_error!("Function not found while attempting to capture a value");
[INFO] [stdout]      |                    ------------------------------------------------------------------------ in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:1361:31
[INFO] [stdout]      |
[INFO] [stdout] 1361 |                     Err(_) => runtime_error!("Failed to get display value"),
[INFO] [stdout]      |                               --------------------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:1832:28
[INFO] [stdout]      |
[INFO] [stdout] 1832 |                       return runtime_error!(
[INFO] [stdout]      |  ____________________________-
[INFO] [stdout] 1833 | |                         "Expected Bool from equality comparison, found '{}'",
[INFO] [stdout] 1834 | |                         other.type_as_string()
[INFO] [stdout] 1835 | |                     );
[INFO] [stdout]      | |_____________________- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:1857:28
[INFO] [stdout]      |
[INFO] [stdout] 1857 |                       return runtime_error!(
[INFO] [stdout]      |  ____________________________-
[INFO] [stdout] 1858 | |                         "Expected Bool from equality comparison, found '{}'",
[INFO] [stdout] 1859 | |                         other.type_as_string()
[INFO] [stdout] 1860 | |                     );
[INFO] [stdout]      | |_____________________- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:1981:34
[INFO] [stdout]      |
[INFO] [stdout] 1981 |             Err(error) => return runtime_error!("Failed to import '{import_name}': {error}"),
[INFO] [stdout]      |                                  ----------------------------------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:1995:24
[INFO] [stdout]      |
[INFO] [stdout] 1995 |                 return runtime_error!("Recursive import of module '{import_name}'");
[INFO] [stdout]      |                        ------------------------------------------------------------ in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 192 | /     runtime_error!(ErrorKind::UnexpectedType {
[INFO] [stdout] 193 | |         expected: expected_str.into(),
[INFO] [stdout] 194 | |         unexpected: unexpected.into(),
[INFO] [stdout] 195 | |     })
[INFO] [stdout]     | |______- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: expected names are: `debug_assertions`, `doc`, `doctest`, `feature`, `miri`, `overflow_checks`, `panic`, `proc_macro`, `relocation_model`, `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`, `unix`, `windows`
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: requested on the command line with `-D unexpected-cfgs`
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:2033:36
[INFO] [stdout]      |
[INFO] [stdout] 2033 |   ...                   return runtime_error!(
[INFO] [stdout]      |  ______________________________-
[INFO] [stdout] 2034 | | ...                       "Expected map for tests in module '{import_name}', found '{}'",
[INFO] [stdout] 2035 | | ...                       other.type_as_string()
[INFO] [stdout] 2036 | | ...                   )
[INFO] [stdout]      | |_______________________- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/io/file.rs:10:9
[INFO] [stdout]     |
[INFO] [stdout] 10  |         runtime_error!("unsupported for this file type")
[INFO] [stdout]     |         ------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/io/file.rs:15:9
[INFO] [stdout]     |
[INFO] [stdout] 15  |         runtime_error!("unsupported for this file type")
[INFO] [stdout]     |         ------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/io/file.rs:25:9
[INFO] [stdout]     |
[INFO] [stdout] 25  |         runtime_error!("unsupported for this file type")
[INFO] [stdout]     |         ------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/io/file.rs:30:9
[INFO] [stdout]     |
[INFO] [stdout] 30  |         runtime_error!("unsupported for this file type")
[INFO] [stdout]     |         ------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/io/file.rs:38:9
[INFO] [stdout]     |
[INFO] [stdout] 38  |         runtime_error!("unsupported for this file type")
[INFO] [stdout]     |         ------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/io/file.rs:43:9
[INFO] [stdout]     |
[INFO] [stdout] 43  |         runtime_error!("unsupported for this file type")
[INFO] [stdout]     |         ------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/io/file.rs:48:9
[INFO] [stdout]     |
[INFO] [stdout] 48  |         runtime_error!("unsupported for this file type")
[INFO] [stdout]     |         ------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/types/iterator.rs:196:13
[INFO] [stdout]     |
[INFO] [stdout] 196 |             runtime_error!("Unbounded ranges can't be used as iterators (range: {range})")
[INFO] [stdout]     |             ------------------------------------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/types/iterator.rs:411:28
[INFO] [stdout]     |
[INFO] [stdout] 411 |             None => return runtime_error!("Expected implementation of @next"),
[INFO] [stdout]     |                            -------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/types/iterator.rs:477:13
[INFO] [stdout]     |
[INFO] [stdout] 477 |             runtime_error!("{} is not an iterator", object.try_borrow()?.object_type())
[INFO] [stdout]     |             --------------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:2103:36
[INFO] [stdout]      |
[INFO] [stdout] 2103 | ...                   return runtime_error!("Index '{index}' not in List");
[INFO] [stdout]      |                              --------------------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/types/map.rs:185:32
[INFO] [stdout]     |
[INFO] [stdout] 185 |                 .ok_or_else(|| make_runtime_error!("Missing VM in map display op"))?
[INFO] [stdout]     |                                --------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `make_runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:2124:20
[INFO] [stdout]      |
[INFO] [stdout] 2124 |             return runtime_error!("Negative indices aren't allowed ('{n}')");
[INFO] [stdout]      |                    --------------------------------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/types/meta_map.rs:247:32
[INFO] [stdout]     |
[INFO] [stdout] 247 |             name.ok_or_else(|| make_runtime_error!("Missing name for named meta entry"))?,
[INFO] [stdout]     |                                -------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `make_runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:2127:24
[INFO] [stdout]      |
[INFO] [stdout] 2127 |                 return runtime_error!("Index out of bounds - index: {n}, size: {size}");
[INFO] [stdout]      |                        ---------------------------------------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/types/meta_map.rs:251:46
[INFO] [stdout]     |
[INFO] [stdout] 251 |             MetaKey::Test(name.ok_or_else(|| make_runtime_error!("Missing name for test"))?)
[INFO] [stdout]     |                                              -------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `make_runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:2175:28
[INFO] [stdout]      |
[INFO] [stdout] 2175 |                     return runtime_error!("Unable to index {}", value.type_as_string());
[INFO] [stdout]      |                            ------------------------------------------------------------ in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/types/meta_map.rs:258:38
[INFO] [stdout]     |
[INFO] [stdout] 258 |         MetaKeyId::Invalid => return runtime_error!("Invalid MetaKeyId"),
[INFO] [stdout]     |                                      ----------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:2183:24
[INFO] [stdout]      |
[INFO] [stdout] 2183 |                   return runtime_error!(
[INFO] [stdout]      |  ________________________-
[INFO] [stdout] 2184 | |                     "Unable to index '{}' with '{}'",
[INFO] [stdout] 2185 | |                     unexpected_value.type_as_string(),
[INFO] [stdout] 2186 | |                     unexpected_index.type_as_string(),
[INFO] [stdout] 2187 | |                 )
[INFO] [stdout]      | |_________________- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/types/object.rs:236:13
[INFO] [stdout]     |
[INFO] [stdout] 236 |             make_runtime_error!("Attempting to borrow an object that is already mutably borrowed")
[INFO] [stdout]     |             -------------------------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `make_runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:2216:34
[INFO] [stdout]      |
[INFO] [stdout] 2216 |             Err(error) => return runtime_error!("Error while preparing meta key: {error}"),
[INFO] [stdout]      |                                  --------------------------------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:2240:38
[INFO] [stdout]      |
[INFO] [stdout] 2240 |                 Err(error) => return runtime_error!("Error while preparing meta key: {error}"),
[INFO] [stdout]      |                                      --------------------------------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/types/object.rs:243:13
[INFO] [stdout]     |
[INFO] [stdout] 243 |             make_runtime_error!("Attempting to borrow an object that is already mutably borrowed")
[INFO] [stdout]     |             -------------------------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `make_runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:2258:34
[INFO] [stdout]      |
[INFO] [stdout] 2258 |             Err(error) => return runtime_error!("Error while preparing meta key: {error}"),
[INFO] [stdout]      |                                  --------------------------------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:2276:38
[INFO] [stdout]      |
[INFO] [stdout] 2276 |                 Err(error) => return runtime_error!("Error while preparing meta key: {error}"),
[INFO] [stdout]      |                                      --------------------------------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/types/object.rs:250:26
[INFO] [stdout]     |
[INFO] [stdout] 250 |             .map_err(|_| make_runtime_error!("Incorrect object type"))
[INFO] [stdout]     |                          -------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `make_runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:2357:28
[INFO] [stdout]      |
[INFO] [stdout] 2357 |                       return runtime_error!(
[INFO] [stdout]      |  ____________________________-
[INFO] [stdout] 2358 | |                         "'{key}' not found in '{}'",
[INFO] [stdout] 2359 | |                         accessed_value.type_as_string()
[INFO] [stdout] 2360 | |                     );
[INFO] [stdout]      | |_____________________- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/types/object.rs:256:26
[INFO] [stdout]     |
[INFO] [stdout] 256 |             .map_err(|_| make_runtime_error!("Incorrect object type"))
[INFO] [stdout]     |                          -------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `make_runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:2380:32
[INFO] [stdout]      |
[INFO] [stdout] 2380 |                         return runtime_error!("'{key}' not found in '{}'", o.object_type());
[INFO] [stdout]      |                                ------------------------------------------------------------ in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:2405:13
[INFO] [stdout]      |
[INFO] [stdout] 2405 |             runtime_error!("'{key}' not found in '{module_name}'")
[INFO] [stdout]      |             ------------------------------------------------------ in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/types/object.rs:453:5
[INFO] [stdout]     |
[INFO] [stdout] 453 |     runtime_error!("{method} is unimplemented for {object_type}")
[INFO] [stdout]     |     ------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:2635:24
[INFO] [stdout]      |
[INFO] [stdout] 2635 |                   return runtime_error!(
[INFO] [stdout]      |  ________________________-
[INFO] [stdout] 2636 | |                     "debug: Expected string to display, found '{}'",
[INFO] [stdout] 2637 | |                     other.type_as_string()
[INFO] [stdout] 2638 | |                 )
[INFO] [stdout]      | |_________________- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/types/range.rs:260:25
[INFO] [stdout]     |
[INFO] [stdout] 260 |             _ => return runtime_error!("KRange::pop_front can only be used with bounded ranges"),
[INFO] [stdout]     |                         ------------------------------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:2684:13
[INFO] [stdout]      |
[INFO] [stdout] 2684 | /             runtime_error!(
[INFO] [stdout] 2685 | |                 "The provided value has a size of '{value_size}', expected '{expected_size}'"
[INFO] [stdout] 2686 | |             )
[INFO] [stdout]      | |_____________- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:2696:13
[INFO] [stdout]      |
[INFO] [stdout] 2696 | /             runtime_error!(
[INFO] [stdout] 2697 | |                 "The provided value has a size of '{value_size}', expected a minimum of '{expected_size}'"
[INFO] [stdout] 2698 | |             )
[INFO] [stdout]      | |_____________- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/types/range.rs:325:25
[INFO] [stdout]     |
[INFO] [stdout] 325 |             _ => return runtime_error!("KRange::pop_back can only be used with bounded ranges"),
[INFO] [stdout]     |                         ----------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:2708:13
[INFO] [stdout]      |
[INFO] [stdout] 2708 |             runtime_error!(ErrorKind::MissingSequenceBuilder)
[INFO] [stdout]      |             ------------------------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:2718:13
[INFO] [stdout]      |
[INFO] [stdout] 2718 |             runtime_error!(ErrorKind::MissingSequenceBuilder)
[INFO] [stdout]      |             ------------------------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/types/value.rs:238:13
[INFO] [stdout]     |
[INFO] [stdout] 238 |             runtime_error!("Failed to write to string")
[INFO] [stdout]     |             ------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:2727:13
[INFO] [stdout]      |
[INFO] [stdout] 2727 |             runtime_error!(ErrorKind::MissingSequenceBuilder)
[INFO] [stdout]      |             ------------------------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/types/value_key.rs:29:13
[INFO] [stdout]     |
[INFO] [stdout] 29  |             runtime_error!("Only hashable values can be used as value keys")
[INFO] [stdout]     |             ---------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:2740:21
[INFO] [stdout]      |
[INFO] [stdout] 2740 |                     runtime_error!(ErrorKind::MissingStringBuilder)
[INFO] [stdout]      |                     ----------------------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/vm.rs:278:20
[INFO] [stdout]     |
[INFO] [stdout] 278 |             return runtime_error!("run_function: the provided value isn't a function");
[INFO] [stdout]     |                    ------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/vm.rs:531:36
[INFO] [stdout]     |
[INFO] [stdout] 531 |                     NotIterable => runtime_error!("{} is not iterable", o_inner.object_type()),
[INFO] [stdout]     |                                    ----------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:2753:13
[INFO] [stdout]      |
[INFO] [stdout] 2753 |             runtime_error!(ErrorKind::MissingStringBuilder)
[INFO] [stdout]      |             ----------------------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/vm.rs:539:17
[INFO] [stdout]     |
[INFO] [stdout] 539 | /                 runtime_error!(
[INFO] [stdout] 540 | |                     "expected iterable value, found '{}'",
[INFO] [stdout] 541 | |                     unexpected.type_as_string(),
[INFO] [stdout] 542 | |                 )
[INFO] [stdout]     | |_________________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:2831:17
[INFO] [stdout]      |
[INFO] [stdout] 2831 |                 runtime_error!(ErrorKind::EmptyCallStack)
[INFO] [stdout]      |                 ----------------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/vm.rs:689:34
[INFO] [stdout]     |
[INFO] [stdout] 689 |             Error { message } => runtime_error!(message)?,
[INFO] [stdout]     |                                  ----------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:2838:26
[INFO] [stdout]      |
[INFO] [stdout] 2838 |             .map_err(|_| make_runtime_error!("Overflow of Koto's stack"))
[INFO] [stdout]      |                          ----------------------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `make_runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/vm.rs:952:13
[INFO] [stdout]     |
[INFO] [stdout] 952 |             runtime_error!("'{name}' not found")
[INFO] [stdout]     |             ------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:1049:32
[INFO] [stdout]      |
[INFO] [stdout] 1049 |                         return runtime_error!("{} is not iterable", o_inner.object_type())
[INFO] [stdout]      |                                ----------------------------------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:2928:5
[INFO] [stdout]      |
[INFO] [stdout] 2928 | /     runtime_error!(ErrorKind::InvalidBinaryOp {
[INFO] [stdout] 2929 | |         lhs: lhs.clone(),
[INFO] [stdout] 2930 | |         rhs: rhs.clone(),
[INFO] [stdout] 2931 | |         op,
[INFO] [stdout] 2932 | |     })
[INFO] [stdout]      | |______- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:1098:32
[INFO] [stdout]      |
[INFO] [stdout] 1098 |                         return runtime_error!(error.to_string());
[INFO] [stdout]      |                                --------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:1298:20
[INFO] [stdout]      |
[INFO] [stdout] 1298 |             return runtime_error!("Function not found while attempting to capture a value");
[INFO] [stdout]      |                    ------------------------------------------------------------------------ in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/io.rs:26:35
[INFO] [stdout]     |
[INFO] [stdout] 26  |                     Err(error) => runtime_error!("io.create: Error while creating file: {error}"),
[INFO] [stdout]     |                                   --------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:1361:31
[INFO] [stdout]      |
[INFO] [stdout] 1361 |                     Err(_) => runtime_error!("Failed to get display value"),
[INFO] [stdout]      |                               --------------------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/io.rs:73:35
[INFO] [stdout]     |
[INFO] [stdout] 73  |                     Err(error) => runtime_error!("io.open: Error while opening path: {error}"),
[INFO] [stdout]     |                                   ------------------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:1832:28
[INFO] [stdout]      |
[INFO] [stdout] 1832 |                       return runtime_error!(
[INFO] [stdout]      |  ____________________________-
[INFO] [stdout] 1833 | |                         "Expected Bool from equality comparison, found '{}'",
[INFO] [stdout] 1834 | |                         other.type_as_string()
[INFO] [stdout] 1835 | |                     );
[INFO] [stdout]      | |_____________________- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/io.rs:75:27
[INFO] [stdout]     |
[INFO] [stdout] 75  |                 Err(_) => runtime_error!("io.open: Failed to canonicalize path"),
[INFO] [stdout]     |                           ------------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:1857:28
[INFO] [stdout]      |
[INFO] [stdout] 1857 |                       return runtime_error!(
[INFO] [stdout]      |  ____________________________-
[INFO] [stdout] 1858 | |                         "Expected Bool from equality comparison, found '{}'",
[INFO] [stdout] 1859 | |                         other.type_as_string()
[INFO] [stdout] 1860 | |                     );
[INFO] [stdout]      | |_____________________- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:1981:34
[INFO] [stdout]      |
[INFO] [stdout] 1981 |             Err(error) => return runtime_error!("Failed to import '{import_name}': {error}"),
[INFO] [stdout]      |                                  ----------------------------------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/io.rs:124:17
[INFO] [stdout]     |
[INFO] [stdout] 124 |                 runtime_error!("io.read_to_string: Unable to read file '{path}': {error}")
[INFO] [stdout]     |                 -------------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:1995:24
[INFO] [stdout]      |
[INFO] [stdout] 1995 |                 return runtime_error!("Recursive import of module '{import_name}'");
[INFO] [stdout]      |                        ------------------------------------------------------------ in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:2033:36
[INFO] [stdout]      |
[INFO] [stdout] 2033 |   ...                   return runtime_error!(
[INFO] [stdout]      |  ______________________________-
[INFO] [stdout] 2034 | | ...                       "Expected map for tests in module '{import_name}', found '{}'",
[INFO] [stdout] 2035 | | ...                       other.type_as_string()
[INFO] [stdout] 2036 | | ...                   )
[INFO] [stdout]      | |_______________________- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/io.rs:136:35
[INFO] [stdout]     |
[INFO] [stdout] 136 |                       Err(error) => runtime_error!(
[INFO] [stdout]     |  ___________________________________-
[INFO] [stdout] 137 | |                         "io.remove_file: Error while removing file '{}': {error}",
[INFO] [stdout] 138 | |                         path.to_string_lossy(),
[INFO] [stdout] 139 | |                     ),
[INFO] [stdout]     | |_____________________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/io.rs:245:28
[INFO] [stdout]     |
[INFO] [stdout] 245 |                     return runtime_error!("Negative seek positions not allowed");
[INFO] [stdout]     |                            ----------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/iterator/adaptors.rs:572:49
[INFO] [stdout]     |
[INFO] [stdout] 572 |                   Ok(unexpected) => Output::Error(make_runtime_error!(format!(
[INFO] [stdout]     |  _________________________________________________-
[INFO] [stdout] 573 | |                     "iterator.keep: Expected a Bool to be returned from the predicate, found '{}'",
[INFO] [stdout] 574 | |                     unexpected.type_as_string()
[INFO] [stdout] 575 | |                 ))),
[INFO] [stdout]     | |__________________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `make_runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/iterator/adaptors.rs:881:45
[INFO] [stdout]     |
[INFO] [stdout] 881 |               Ok(unexpected) => Output::Error(make_runtime_error!(format!(
[INFO] [stdout]     |  _____________________________________________-
[INFO] [stdout] 882 | |                 "expected a Bool to be returned from the predicate, found '{}'",
[INFO] [stdout] 883 | |                 unexpected.type_as_string()
[INFO] [stdout] 884 | |             ))),
[INFO] [stdout]     | |______________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `make_runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/iterator.rs:121:31
[INFO] [stdout]     |
[INFO] [stdout] 121 |                     Err(e) => runtime_error!("iterator.chunks: {}", e),
[INFO] [stdout]     |                               ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/iterator.rs:637:31
[INFO] [stdout]     |
[INFO] [stdout] 637 |                     Err(e) => runtime_error!("iterator.reversed: {}", e),
[INFO] [stdout]     |                               ------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:2103:36
[INFO] [stdout]      |
[INFO] [stdout] 2103 | ...                   return runtime_error!("Index '{index}' not in List");
[INFO] [stdout]      |                              --------------------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/iterator.rs:674:31
[INFO] [stdout]     |
[INFO] [stdout] 674 |                     Err(e) => runtime_error!("iterator.step: {}", e),
[INFO] [stdout]     |                               -------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:2124:20
[INFO] [stdout]      |
[INFO] [stdout] 2124 |             return runtime_error!("Negative indices aren't allowed ('{n}')");
[INFO] [stdout]      |                    --------------------------------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:2127:24
[INFO] [stdout]      |
[INFO] [stdout] 2127 |                 return runtime_error!("Index out of bounds - index: {n}, size: {size}");
[INFO] [stdout]      |                        ---------------------------------------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:2175:28
[INFO] [stdout]      |
[INFO] [stdout] 2175 |                     return runtime_error!("Unable to index {}", value.type_as_string());
[INFO] [stdout]      |                            ------------------------------------------------------------ in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/iterator.rs:831:31
[INFO] [stdout]     |
[INFO] [stdout] 831 |                     Err(e) => runtime_error!("iterator.windows: {}", e),
[INFO] [stdout]     |                               ----------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:2183:24
[INFO] [stdout]      |
[INFO] [stdout] 2183 |                   return runtime_error!(
[INFO] [stdout]      |  ________________________-
[INFO] [stdout] 2184 | |                     "Unable to index '{}' with '{}'",
[INFO] [stdout] 2185 | |                     unexpected_value.type_as_string(),
[INFO] [stdout] 2186 | |                     unexpected_index.type_as_string(),
[INFO] [stdout] 2187 | |                 )
[INFO] [stdout]      | |_________________- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:2216:34
[INFO] [stdout]      |
[INFO] [stdout] 2216 |             Err(error) => return runtime_error!("Error while preparing meta key: {error}"),
[INFO] [stdout]      |                                  --------------------------------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:2240:38
[INFO] [stdout]      |
[INFO] [stdout] 2240 |                 Err(error) => return runtime_error!("Error while preparing meta key: {error}"),
[INFO] [stdout]      |                                      --------------------------------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/iterator.rs:963:23
[INFO] [stdout]     |
[INFO] [stdout] 963 |           (other, _) => runtime_error!(
[INFO] [stdout]     |  _______________________-
[INFO] [stdout] 964 | |             "Expected Bool from '<' comparison, found '{}'",
[INFO] [stdout] 965 | |             other.type_as_string()
[INFO] [stdout] 966 | |         ),
[INFO] [stdout]     | |_________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:2258:34
[INFO] [stdout]      |
[INFO] [stdout] 2258 |             Err(error) => return runtime_error!("Error while preparing meta key: {error}"),
[INFO] [stdout]      |                                  --------------------------------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/iterator.rs:990:23
[INFO] [stdout]     |
[INFO] [stdout] 990 |           (other, _) => runtime_error!(
[INFO] [stdout]     |  _______________________-
[INFO] [stdout] 991 | |             "Expected Bool from '<' comparison, found '{}'",
[INFO] [stdout] 992 | |             other.type_as_string()
[INFO] [stdout] 993 | |         ),
[INFO] [stdout]     | |_________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:2276:38
[INFO] [stdout]      |
[INFO] [stdout] 2276 |                 Err(error) => return runtime_error!("Error while preparing meta key: {error}"),
[INFO] [stdout]      |                                      --------------------------------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:2357:28
[INFO] [stdout]      |
[INFO] [stdout] 2357 |                       return runtime_error!(
[INFO] [stdout]      |  ____________________________-
[INFO] [stdout] 2358 | |                         "'{key}' not found in '{}'",
[INFO] [stdout] 2359 | |                         accessed_value.type_as_string()
[INFO] [stdout] 2360 | |                     );
[INFO] [stdout]      | |_____________________- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/list.rs:41:36
[INFO] [stdout]     |
[INFO] [stdout] 41  |   ...                   return runtime_error!(
[INFO] [stdout]     |  ______________________________-
[INFO] [stdout] 42  | | ...                       "list.contains: Expected Bool from comparison, found '{}'",
[INFO] [stdout] 43  | | ...                       unexpected.type_as_string()
[INFO] [stdout] 44  | | ...                   )
[INFO] [stdout]     | |_______________________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:2380:32
[INFO] [stdout]      |
[INFO] [stdout] 2380 |                         return runtime_error!("'{key}' not found in '{}'", o.object_type());
[INFO] [stdout]      |                                ------------------------------------------------------------ in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:2405:13
[INFO] [stdout]      |
[INFO] [stdout] 2405 |             runtime_error!("'{key}' not found in '{module_name}'")
[INFO] [stdout]      |             ------------------------------------------------------ in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/list.rs:142:28
[INFO] [stdout]     |
[INFO] [stdout] 142 |                     return runtime_error!("list.insert: Index out of bounds");
[INFO] [stdout]     |                            -------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:2635:24
[INFO] [stdout]      |
[INFO] [stdout] 2635 |                   return runtime_error!(
[INFO] [stdout]      |  ________________________-
[INFO] [stdout] 2636 | |                     "debug: Expected string to display, found '{}'",
[INFO] [stdout] 2637 | |                     other.type_as_string()
[INFO] [stdout] 2638 | |                 )
[INFO] [stdout]      | |_________________- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:2684:13
[INFO] [stdout]      |
[INFO] [stdout] 2684 | /             runtime_error!(
[INFO] [stdout] 2685 | |                 "The provided value has a size of '{value_size}', expected '{expected_size}'"
[INFO] [stdout] 2686 | |             )
[INFO] [stdout]      | |_____________- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/list.rs:204:28
[INFO] [stdout]     |
[INFO] [stdout] 204 |                       return runtime_error!(
[INFO] [stdout]     |  ____________________________-
[INFO] [stdout] 205 | |                         "list.remove: Index out of bounds - \
[INFO] [stdout] 206 | |                          the index is {index} but the List only has {} elements",
[INFO] [stdout] 207 | |                         l.data().len(),
[INFO] [stdout] 208 | |                     );
[INFO] [stdout]     | |_____________________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:2696:13
[INFO] [stdout]      |
[INFO] [stdout] 2696 | /             runtime_error!(
[INFO] [stdout] 2697 | |                 "The provided value has a size of '{value_size}', expected a minimum of '{expected_size}'"
[INFO] [stdout] 2698 | |             )
[INFO] [stdout]      | |_____________- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:2708:13
[INFO] [stdout]      |
[INFO] [stdout] 2708 |             runtime_error!(ErrorKind::MissingSequenceBuilder)
[INFO] [stdout]      |             ------------------------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:2718:13
[INFO] [stdout]      |
[INFO] [stdout] 2718 |             runtime_error!(ErrorKind::MissingSequenceBuilder)
[INFO] [stdout]      |             ------------------------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:2727:13
[INFO] [stdout]      |
[INFO] [stdout] 2727 |             runtime_error!(ErrorKind::MissingSequenceBuilder)
[INFO] [stdout]      |             ------------------------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/map.rs:218:42
[INFO] [stdout]     |
[INFO] [stdout] 218 | ...                   error = Some(runtime_error!("Invalid map key encountered"));
[INFO] [stdout]     |                                    --------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:2740:21
[INFO] [stdout]      |
[INFO] [stdout] 2740 |                     runtime_error!(ErrorKind::MissingStringBuilder)
[INFO] [stdout]      |                     ----------------------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:2753:13
[INFO] [stdout]      |
[INFO] [stdout] 2753 |             runtime_error!(ErrorKind::MissingStringBuilder)
[INFO] [stdout]      |             ----------------------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:2831:17
[INFO] [stdout]      |
[INFO] [stdout] 2831 |                 runtime_error!(ErrorKind::EmptyCallStack)
[INFO] [stdout]      |                 ----------------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:2838:26
[INFO] [stdout]      |
[INFO] [stdout] 2838 |             .map_err(|_| make_runtime_error!("Overflow of Koto's stack"))
[INFO] [stdout]      |                          ----------------------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `make_runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/os.rs:60:32
[INFO] [stdout]     |
[INFO] [stdout] 60  |                 None => return runtime_error!("time offset is out of range: {offset}"),
[INFO] [stdout]     |                                ------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]     --> src/error.rs:159:15
[INFO] [stdout]      |
[INFO] [stdout] 159  |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]      |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]     ::: src/vm.rs:2928:5
[INFO] [stdout]      |
[INFO] [stdout] 2928 | /     runtime_error!(ErrorKind::InvalidBinaryOp {
[INFO] [stdout] 2929 | |         lhs: lhs.clone(),
[INFO] [stdout] 2930 | |         rhs: rhs.clone(),
[INFO] [stdout] 2931 | |         op,
[INFO] [stdout] 2932 | |     })
[INFO] [stdout]      | |______- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/os.rs:68:21
[INFO] [stdout]     |
[INFO] [stdout] 68  |             None => runtime_error!("timestamp in seconds is out of range: {seconds}"),
[INFO] [stdout]     |                     ----------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/io.rs:26:35
[INFO] [stdout]     |
[INFO] [stdout] 26  |                     Err(error) => runtime_error!("io.create: Error while creating file: {error}"),
[INFO] [stdout]     |                                   --------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/io.rs:73:35
[INFO] [stdout]     |
[INFO] [stdout] 73  |                     Err(error) => runtime_error!("io.open: Error while opening path: {error}"),
[INFO] [stdout]     |                                   ------------------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/io.rs:75:27
[INFO] [stdout]     |
[INFO] [stdout] 75  |                 Err(_) => runtime_error!("io.open: Failed to canonicalize path"),
[INFO] [stdout]     |                           ------------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/range.rs:49:22
[INFO] [stdout]     |
[INFO] [stdout] 49  |                 _ => runtime_error!("range.expanded can't be used with '{r}'"),
[INFO] [stdout]     |                      --------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/range.rs:83:25
[INFO] [stdout]     |
[INFO] [stdout] 83  |                 None => runtime_error!("range.size can't be used with '{r}'"),
[INFO] [stdout]     |                         ----------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/io.rs:124:17
[INFO] [stdout]     |
[INFO] [stdout] 124 |                 runtime_error!("io.read_to_string: Unable to read file '{path}': {error}")
[INFO] [stdout]     |                 -------------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/range.rs:113:26
[INFO] [stdout]     |
[INFO] [stdout] 113 |                     _ => runtime_error!("range.union can't be used with '{r}'"),
[INFO] [stdout]     |                          ------------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/io.rs:136:35
[INFO] [stdout]     |
[INFO] [stdout] 136 |                       Err(error) => runtime_error!(
[INFO] [stdout]     |  ___________________________________-
[INFO] [stdout] 137 | |                         "io.remove_file: Error while removing file '{}': {error}",
[INFO] [stdout] 138 | |                         path.to_string_lossy(),
[INFO] [stdout] 139 | |                     ),
[INFO] [stdout]     | |_____________________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/range.rs:126:22
[INFO] [stdout]     |
[INFO] [stdout] 126 |                 _ => runtime_error!("range.union can't be used with '{a}' and '{b}'"),
[INFO] [stdout]     |                      ---------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/io.rs:245:28
[INFO] [stdout]     |
[INFO] [stdout] 245 |                     return runtime_error!("Negative seek positions not allowed");
[INFO] [stdout]     |                            ----------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/string/format.rs:311:32
[INFO] [stdout]     |
[INFO] [stdout] 311 |                 None => return runtime_error!("Not enough arguments for format string"),
[INFO] [stdout]     |                                -------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/string/format.rs:315:32
[INFO] [stdout]     |
[INFO] [stdout] 315 |                 None => return runtime_error!("Missing argument for index {n}"),
[INFO] [stdout]     |                                ------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/iterator/adaptors.rs:572:49
[INFO] [stdout]     |
[INFO] [stdout] 572 |                   Ok(unexpected) => Output::Error(make_runtime_error!(format!(
[INFO] [stdout]     |  _________________________________________________-
[INFO] [stdout] 573 | |                     "iterator.keep: Expected a Bool to be returned from the predicate, found '{}'",
[INFO] [stdout] 574 | |                     unexpected.type_as_string()
[INFO] [stdout] 575 | |                 ))),
[INFO] [stdout]     | |__________________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `make_runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/string/format.rs:320:36
[INFO] [stdout]     |
[INFO] [stdout] 320 |                     None => return runtime_error!("Key '{id}' not found in map"),
[INFO] [stdout]     |                                    --------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/iterator/adaptors.rs:881:45
[INFO] [stdout]     |
[INFO] [stdout] 881 |               Ok(unexpected) => Output::Error(make_runtime_error!(format!(
[INFO] [stdout]     |  _____________________________________________-
[INFO] [stdout] 882 | |                 "expected a Bool to be returned from the predicate, found '{}'",
[INFO] [stdout] 883 | |                 unexpected.type_as_string()
[INFO] [stdout] 884 | |             ))),
[INFO] [stdout]     | |______________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `make_runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/string/format.rs:323:28
[INFO] [stdout]     |
[INFO] [stdout] 323 |                       return runtime_error!(
[INFO] [stdout]     |  ____________________________-
[INFO] [stdout] 324 | |                         "Expected map as first argument, found '{}'",
[INFO] [stdout] 325 | |                         other.type_as_string()
[INFO] [stdout] 326 | |                     )
[INFO] [stdout]     | |_____________________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/iterator.rs:121:31
[INFO] [stdout]     |
[INFO] [stdout] 121 |                     Err(e) => runtime_error!("iterator.chunks: {}", e),
[INFO] [stdout]     |                               ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/string/format.rs:328:32
[INFO] [stdout]     |
[INFO] [stdout] 328 |                 None => return runtime_error!("Expected map as first argument"),
[INFO] [stdout]     |                                ------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/string/format.rs:330:49
[INFO] [stdout]     |
[INFO] [stdout] 330 |             FormatToken::Error(error) => return runtime_error!("Invalid format string: {error}"),
[INFO] [stdout]     |                                                 ------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/iterator.rs:637:31
[INFO] [stdout]     |
[INFO] [stdout] 637 |                     Err(e) => runtime_error!("iterator.reversed: {}", e),
[INFO] [stdout]     |                               ------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/iterator.rs:674:31
[INFO] [stdout]     |
[INFO] [stdout] 674 |                     Err(e) => runtime_error!("iterator.step: {}", e),
[INFO] [stdout]     |                               -------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/string/format.rs:369:24
[INFO] [stdout]     |
[INFO] [stdout] 369 |                   return runtime_error!(
[INFO] [stdout]     |  ________________________-
[INFO] [stdout] 370 | |                     "Expected string from @display, found '{}'",
[INFO] [stdout] 371 | |                     other.type_as_string()
[INFO] [stdout] 372 | |                 )
[INFO] [stdout]     | |_________________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/iterator.rs:831:31
[INFO] [stdout]     |
[INFO] [stdout] 831 |                     Err(e) => runtime_error!("iterator.windows: {}", e),
[INFO] [stdout]     |                               ----------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/iterator.rs:963:23
[INFO] [stdout]     |
[INFO] [stdout] 963 |           (other, _) => runtime_error!(
[INFO] [stdout]     |  _______________________-
[INFO] [stdout] 964 | |             "Expected Bool from '<' comparison, found '{}'",
[INFO] [stdout] 965 | |             other.type_as_string()
[INFO] [stdout] 966 | |         ),
[INFO] [stdout]     | |_________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/iterator.rs:990:23
[INFO] [stdout]     |
[INFO] [stdout] 990 |           (other, _) => runtime_error!(
[INFO] [stdout]     |  _______________________-
[INFO] [stdout] 991 | |             "Expected Bool from '<' comparison, found '{}'",
[INFO] [stdout] 992 | |             other.type_as_string()
[INFO] [stdout] 993 | |         ),
[INFO] [stdout]     | |_________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/list.rs:41:36
[INFO] [stdout]     |
[INFO] [stdout] 41  |   ...                   return runtime_error!(
[INFO] [stdout]     |  ______________________________-
[INFO] [stdout] 42  | | ...                       "list.contains: Expected Bool from comparison, found '{}'",
[INFO] [stdout] 43  | | ...                       unexpected.type_as_string()
[INFO] [stdout] 44  | | ...                   )
[INFO] [stdout]     | |_______________________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/list.rs:142:28
[INFO] [stdout]     |
[INFO] [stdout] 142 |                     return runtime_error!("list.insert: Index out of bounds");
[INFO] [stdout]     |                            -------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/list.rs:204:28
[INFO] [stdout]     |
[INFO] [stdout] 204 |                       return runtime_error!(
[INFO] [stdout]     |  ____________________________-
[INFO] [stdout] 205 | |                         "list.remove: Index out of bounds - \
[INFO] [stdout] 206 | |                          the index is {index} but the List only has {} elements",
[INFO] [stdout] 207 | |                         l.data().len(),
[INFO] [stdout] 208 | |                     );
[INFO] [stdout]     | |_____________________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/string/iterators.rs:219:37
[INFO] [stdout]     |
[INFO] [stdout] 219 |                           let error = make_runtime_error!(format!(
[INFO] [stdout]     |  _____________________________________-
[INFO] [stdout] 220 | |                             "string.split: Expected a Bool from the match function, found '{}'",
[INFO] [stdout] 221 | |                             unexpected.type_as_string()
[INFO] [stdout] 222 | |                         ));
[INFO] [stdout]     | |__________________________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `make_runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/string.rs:94:42
[INFO] [stdout]     |
[INFO] [stdout] 94  |                         Err(_) => return runtime_error!("'{n}' is out of the valid byte range"),
[INFO] [stdout]     |                                          ------------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/string.rs:104:27
[INFO] [stdout]     |
[INFO] [stdout] 104 |                 Err(_) => runtime_error!("Input failed UTF-8 validation"),
[INFO] [stdout]     |                           ----------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/string.rs:207:25
[INFO] [stdout]     |
[INFO] [stdout] 207 |                         runtime_error!("string.to_number: Failed to convert '{s}'")
[INFO] [stdout]     |                         ----------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/test.rs:14:32
[INFO] [stdout]     |
[INFO] [stdout] 14  |                         return runtime_error!("Assertion failed");
[INFO] [stdout]     |                                ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/test.rs:31:21
[INFO] [stdout]     |
[INFO] [stdout] 31  | /                     runtime_error!(
[INFO] [stdout] 32  | |                         "Assertion failed, '{}' is not equal to '{}'",
[INFO] [stdout] 33  | |                         ctx.vm.value_to_string(&a)?,
[INFO] [stdout] 34  | |                         ctx.vm.value_to_string(&b)?,
[INFO] [stdout] 35  | |                     )
[INFO] [stdout]     | |_____________________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/test.rs:54:21
[INFO] [stdout]     |
[INFO] [stdout] 54  | /                     runtime_error!(
[INFO] [stdout] 55  | |                         "Assertion failed, '{}' should not be equal to '{}'",
[INFO] [stdout] 56  | |                         ctx.vm.value_to_string(&a)?,
[INFO] [stdout] 57  | |                         ctx.vm.value_to_string(&b)?
[INFO] [stdout] 58  | |                     )
[INFO] [stdout]     | |_____________________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/test.rs:98:9
[INFO] [stdout]     |
[INFO] [stdout] 98  | /         runtime_error!(
[INFO] [stdout] 99  | |             "Assertion failed, '{a}' and '{b}' are not within {allowed_diff} of each other"
[INFO] [stdout] 100 | |         )
[INFO] [stdout]     | |_________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/value_sort.rs:41:27
[INFO] [stdout]     |
[INFO] [stdout] 41  |               unexpected => runtime_error!(
[INFO] [stdout]     |  ___________________________-
[INFO] [stdout] 42  | |                 "Expected Bool from > comparison, found '{}'",
[INFO] [stdout] 43  | |                 unexpected.type_as_string()
[INFO] [stdout] 44  | |             ),
[INFO] [stdout]     | |_____________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/value_sort.rs:47:13
[INFO] [stdout]     |
[INFO] [stdout] 47  | /             runtime_error!(
[INFO] [stdout] 48  | |                 "Expected Bool from < comparison, found '{}'",
[INFO] [stdout] 49  | |                 unexpected.type_as_string()
[INFO] [stdout] 50  | |             )
[INFO] [stdout]     | |_____________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/map.rs:218:42
[INFO] [stdout]     |
[INFO] [stdout] 218 | ...                   error = Some(runtime_error!("Invalid map key encountered"));
[INFO] [stdout]     |                                    --------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/os.rs:60:32
[INFO] [stdout]     |
[INFO] [stdout] 60  |                 None => return runtime_error!("time offset is out of range: {offset}"),
[INFO] [stdout]     |                                ------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/os.rs:68:21
[INFO] [stdout]     |
[INFO] [stdout] 68  |             None => runtime_error!("timestamp in seconds is out of range: {seconds}"),
[INFO] [stdout]     |                     ----------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/range.rs:49:22
[INFO] [stdout]     |
[INFO] [stdout] 49  |                 _ => runtime_error!("range.expanded can't be used with '{r}'"),
[INFO] [stdout]     |                      --------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/range.rs:83:25
[INFO] [stdout]     |
[INFO] [stdout] 83  |                 None => runtime_error!("range.size can't be used with '{r}'"),
[INFO] [stdout]     |                         ----------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/range.rs:113:26
[INFO] [stdout]     |
[INFO] [stdout] 113 |                     _ => runtime_error!("range.union can't be used with '{r}'"),
[INFO] [stdout]     |                          ------------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/range.rs:126:22
[INFO] [stdout]     |
[INFO] [stdout] 126 |                 _ => runtime_error!("range.union can't be used with '{a}' and '{b}'"),
[INFO] [stdout]     |                      ---------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/string/format.rs:311:32
[INFO] [stdout]     |
[INFO] [stdout] 311 |                 None => return runtime_error!("Not enough arguments for format string"),
[INFO] [stdout]     |                                -------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/string/format.rs:315:32
[INFO] [stdout]     |
[INFO] [stdout] 315 |                 None => return runtime_error!("Missing argument for index {n}"),
[INFO] [stdout]     |                                ------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/string/format.rs:320:36
[INFO] [stdout]     |
[INFO] [stdout] 320 |                     None => return runtime_error!("Key '{id}' not found in map"),
[INFO] [stdout]     |                                    --------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/string/format.rs:323:28
[INFO] [stdout]     |
[INFO] [stdout] 323 |                       return runtime_error!(
[INFO] [stdout]     |  ____________________________-
[INFO] [stdout] 324 | |                         "Expected map as first argument, found '{}'",
[INFO] [stdout] 325 | |                         other.type_as_string()
[INFO] [stdout] 326 | |                     )
[INFO] [stdout]     | |_____________________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/string/format.rs:328:32
[INFO] [stdout]     |
[INFO] [stdout] 328 |                 None => return runtime_error!("Expected map as first argument"),
[INFO] [stdout]     |                                ------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/string/format.rs:330:49
[INFO] [stdout]     |
[INFO] [stdout] 330 |             FormatToken::Error(error) => return runtime_error!("Invalid format string: {error}"),
[INFO] [stdout]     |                                                 ------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/string/format.rs:369:24
[INFO] [stdout]     |
[INFO] [stdout] 369 |                   return runtime_error!(
[INFO] [stdout]     |  ________________________-
[INFO] [stdout] 370 | |                     "Expected string from @display, found '{}'",
[INFO] [stdout] 371 | |                     other.type_as_string()
[INFO] [stdout] 372 | |                 )
[INFO] [stdout]     | |_________________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/string/iterators.rs:219:37
[INFO] [stdout]     |
[INFO] [stdout] 219 |                           let error = make_runtime_error!(format!(
[INFO] [stdout]     |  _____________________________________-
[INFO] [stdout] 220 | |                             "string.split: Expected a Bool from the match function, found '{}'",
[INFO] [stdout] 221 | |                             unexpected.type_as_string()
[INFO] [stdout] 222 | |                         ));
[INFO] [stdout]     | |__________________________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `make_runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/string.rs:94:42
[INFO] [stdout]     |
[INFO] [stdout] 94  |                         Err(_) => return runtime_error!("'{n}' is out of the valid byte range"),
[INFO] [stdout]     |                                          ------------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/string.rs:104:27
[INFO] [stdout]     |
[INFO] [stdout] 104 |                 Err(_) => runtime_error!("Input failed UTF-8 validation"),
[INFO] [stdout]     |                           ----------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/string.rs:207:25
[INFO] [stdout]     |
[INFO] [stdout] 207 |                         runtime_error!("string.to_number: Failed to convert '{s}'")
[INFO] [stdout]     |                         ----------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |         #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/test.rs:14:32
[INFO] [stdout]     |
[INFO] [stdout] 14  |                         return runtime_error!("Assertion failed");
[INFO] [stdout]     |                                ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/test.rs:31:21
[INFO] [stdout]     |
[INFO] [stdout] 31  | /                     runtime_error!(
[INFO] [stdout] 32  | |                         "Assertion failed, '{}' is not equal to '{}'",
[INFO] [stdout] 33  | |                         ctx.vm.value_to_string(&a)?,
[INFO] [stdout] 34  | |                         ctx.vm.value_to_string(&b)?,
[INFO] [stdout] 35  | |                     )
[INFO] [stdout]     | |_____________________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/test.rs:54:21
[INFO] [stdout]     |
[INFO] [stdout] 54  | /                     runtime_error!(
[INFO] [stdout] 55  | |                         "Assertion failed, '{}' should not be equal to '{}'",
[INFO] [stdout] 56  | |                         ctx.vm.value_to_string(&a)?,
[INFO] [stdout] 57  | |                         ctx.vm.value_to_string(&b)?
[INFO] [stdout] 58  | |                     )
[INFO] [stdout]     | |_____________________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/test.rs:98:9
[INFO] [stdout]     |
[INFO] [stdout] 98  | /         runtime_error!(
[INFO] [stdout] 99  | |             "Assertion failed, '{a}' and '{b}' are not within {allowed_diff} of each other"
[INFO] [stdout] 100 | |         )
[INFO] [stdout]     | |_________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/value_sort.rs:41:27
[INFO] [stdout]     |
[INFO] [stdout] 41  |               unexpected => runtime_error!(
[INFO] [stdout]     |  ___________________________-
[INFO] [stdout] 42  | |                 "Expected Bool from > comparison, found '{}'",
[INFO] [stdout] 43  | |                 unexpected.type_as_string()
[INFO] [stdout] 44  | |             ),
[INFO] [stdout]     | |_____________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `panic_on_runtime_error`
[INFO] [stdout]    --> src/error.rs:159:15
[INFO] [stdout]     |
[INFO] [stdout] 159 |           #[cfg(panic_on_runtime_error)]
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/core_lib/value_sort.rs:47:13
[INFO] [stdout]     |
[INFO] [stdout] 47  | /             runtime_error!(
[INFO] [stdout] 48  | |                 "Expected Bool from < comparison, found '{}'",
[INFO] [stdout] 49  | |                 unexpected.type_as_string()
[INFO] [stdout] 50  | |             )
[INFO] [stdout]     | |_____________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(panic_on_runtime_error)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `$crate::make_runtime_error` which comes from the expansion of the macro `runtime_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: use of deprecated method `indexmap::IndexMap::<K, V, S>::remove`: `remove` disrupts the map order -- use `swap_remove` or `shift_remove` for explicit behavior.
[INFO] [stdout]    --> src/types/map.rs:237:39
[INFO] [stdout]     |
[INFO] [stdout] 237 |         assert!(matches!(m.data_mut().remove("test"), Some(Value::Null)));
[INFO] [stdout]     |                                       ^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: `#[warn(deprecated)]` on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: aborting due to 102 previous errors
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `koto_runtime` (lib) due to 103 previous errors
[INFO] [stderr] warning: build failed, waiting for other jobs to finish...
[INFO] [stdout] error: aborting due to 102 previous errors; 1 warning emitted
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `koto_runtime` (lib test) due to 103 previous errors; 1 warning emitted
[INFO] running `Command { std: "docker" "inspect" "4bccff5c4d3b1458772941f4a7e35099f4e0e37987425308e9b9613930dd8665", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "4bccff5c4d3b1458772941f4a7e35099f4e0e37987425308e9b9613930dd8665", kill_on_drop: false }`
[INFO] [stdout] 4bccff5c4d3b1458772941f4a7e35099f4e0e37987425308e9b9613930dd8665
