[INFO] fetching crate fidget-rhai 0.4.1... [INFO] checking fidget-rhai-0.4.1 against try#724e78794d2cf06eef820a24c9a4608d63435e1d for pr-149145 [INFO] extracting crate fidget-rhai 0.4.1 into /workspace/builds/worker-7-tc2/source [INFO] started tweaking crates.io crate fidget-rhai 0.4.1 [INFO] finished tweaking crates.io crate fidget-rhai 0.4.1 [INFO] tweaked toml for crates.io crate fidget-rhai 0.4.1 written to /workspace/builds/worker-7-tc2/source/Cargo.toml [INFO] validating manifest of crates.io crate fidget-rhai 0.4.1 on toolchain 724e78794d2cf06eef820a24c9a4608d63435e1d [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+724e78794d2cf06eef820a24c9a4608d63435e1d" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] crate crates.io crate fidget-rhai 0.4.1 already has a lockfile, it will not be regenerated [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+724e78794d2cf06eef820a24c9a4608d63435e1d" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-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:94a0c148923f5b2b52a63ef0eeb1882ad339ab61bce784c8077cbe41c61feb6c" "/opt/rustwide/cargo-home/bin/cargo" "+724e78794d2cf06eef820a24c9a4608d63435e1d" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] fecefec0a373026dd9a850bab3d9e05a71632408f77cb0677efcf8a3149ba368 [INFO] running `Command { std: "docker" "start" "-a" "fecefec0a373026dd9a850bab3d9e05a71632408f77cb0677efcf8a3149ba368", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "fecefec0a373026dd9a850bab3d9e05a71632408f77cb0677efcf8a3149ba368", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "fecefec0a373026dd9a850bab3d9e05a71632408f77cb0677efcf8a3149ba368", kill_on_drop: false }` [INFO] [stdout] fecefec0a373026dd9a850bab3d9e05a71632408f77cb0677efcf8a3149ba368 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:94a0c148923f5b2b52a63ef0eeb1882ad339ab61bce784c8077cbe41c61feb6c" "/opt/rustwide/cargo-home/bin/cargo" "+724e78794d2cf06eef820a24c9a4608d63435e1d" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] 1f90ef71fe4eb993de4253088c1918ecd67c34915999c0dd853423d5964c3512 [INFO] running `Command { std: "docker" "start" "-a" "1f90ef71fe4eb993de4253088c1918ecd67c34915999c0dd853423d5964c3512", kill_on_drop: false }` [INFO] [stderr] Compiling serde v1.0.219 [INFO] [stderr] Compiling owo-colors v4.2.2 [INFO] [stderr] Compiling unsynn v0.1.1 [INFO] [stderr] Compiling libc v0.2.174 [INFO] [stderr] Compiling portable-atomic v1.11.1 [INFO] [stderr] Checking facet-core v0.28.1 [INFO] [stderr] Checking approx v0.5.1 [INFO] [stderr] Compiling strum_macros v0.27.2 [INFO] [stderr] Checking num-rational v0.4.2 [INFO] [stderr] Compiling nalgebra-macros v0.3.0 [INFO] [stderr] Compiling ahash v0.8.12 [INFO] [stderr] Compiling smartstring v1.0.1 [INFO] [stderr] Checking rand v0.9.2 [INFO] [stderr] Compiling enum-map-derive v0.17.0 [INFO] [stderr] Checking rayon v1.10.0 [INFO] [stderr] Checking ordered-float v5.0.0 [INFO] [stderr] Checking spin v0.5.2 [INFO] [stderr] Checking workspace-hack v0.1.0 [INFO] [stderr] Compiling rhai_codegen v2.2.0 [INFO] [stderr] Checking no-std-compat v0.4.1 [INFO] [stderr] Checking thin-vec v0.2.14 [INFO] [stderr] Checking heck v0.5.0 [INFO] [stderr] Checking enum-map v2.7.3 [INFO] [stderr] Compiling getrandom v0.2.16 [INFO] [stderr] Compiling const-random-macro v0.1.16 [INFO] [stderr] Compiling facet-macros-parse v0.28.1 [INFO] [stderr] Checking once_cell v1.21.3 [INFO] [stderr] Checking const-random v0.1.18 [INFO] [stderr] Checking rhai v1.21.0 [INFO] [stderr] Compiling facet-macros-emit v0.28.1 [INFO] [stderr] Checking strum v0.27.2 [INFO] [stderr] Checking num-complex v0.4.6 [INFO] [stderr] Compiling facet-macros v0.28.1 [INFO] [stderr] Checking simba v0.9.0 [INFO] [stderr] Checking facet-reflect v0.28.1 [INFO] [stderr] Checking facet v0.28.1 [INFO] [stderr] Checking nalgebra v0.34.0 [INFO] [stderr] Checking fidget-core v0.4.1 [INFO] [stderr] Checking fidget-shapes v0.4.1 [INFO] [stderr] Checking fidget-rhai v0.4.1 (/opt/rustwide/workdir) [INFO] [stdout] error[E0659]: `NativeCallContext` is ambiguous [INFO] [stdout] --> src/tree.rs:153:17 [INFO] [stdout] | [INFO] [stdout] 153 | use NativeCallContext; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and a macro-expanded name in the same module during import or macro resolution [INFO] [stdout] note: `NativeCallContext` could refer to the struct imported here [INFO] [stdout] --> src/tree.rs:152:17 [INFO] [stdout] | [INFO] [stdout] 152 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 210 | define_binary_fns!(add, Add); [INFO] [stdout] | ---------------------------- in this macro invocation [INFO] [stdout] = help: consider adding an explicit import of `NativeCallContext` to disambiguate [INFO] [stdout] note: `NativeCallContext` could also refer to the struct imported here [INFO] [stdout] --> src/tree.rs:152:17 [INFO] [stdout] | [INFO] [stdout] 152 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 210 | define_binary_fns!(add, Add); [INFO] [stdout] | ---------------------------- in this macro invocation [INFO] [stdout] = help: consider adding an explicit import of `NativeCallContext` to disambiguate [INFO] [stdout] = note: this error originates in the macro `define_binary_fns` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `NativeCallContext` is ambiguous [INFO] [stdout] --> src/tree.rs:153:17 [INFO] [stdout] | [INFO] [stdout] 153 | use NativeCallContext; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and a macro-expanded name in the same module during import or macro resolution [INFO] [stdout] note: `NativeCallContext` could refer to the struct imported here [INFO] [stdout] --> src/tree.rs:152:17 [INFO] [stdout] | [INFO] [stdout] 152 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 211 | define_binary_fns!(sub, Sub); [INFO] [stdout] | ---------------------------- in this macro invocation [INFO] [stdout] = help: consider adding an explicit import of `NativeCallContext` to disambiguate [INFO] [stdout] note: `NativeCallContext` could also refer to the struct imported here [INFO] [stdout] --> src/tree.rs:152:17 [INFO] [stdout] | [INFO] [stdout] 152 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 211 | define_binary_fns!(sub, Sub); [INFO] [stdout] | ---------------------------- in this macro invocation [INFO] [stdout] = help: consider adding an explicit import of `NativeCallContext` to disambiguate [INFO] [stdout] = note: this error originates in the macro `define_binary_fns` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `NativeCallContext` is ambiguous [INFO] [stdout] --> src/tree.rs:153:17 [INFO] [stdout] | [INFO] [stdout] 153 | use NativeCallContext; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and a macro-expanded name in the same module during import or macro resolution [INFO] [stdout] note: `NativeCallContext` could refer to the struct imported here [INFO] [stdout] --> src/tree.rs:152:17 [INFO] [stdout] | [INFO] [stdout] 152 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 212 | define_binary_fns!(mul, Mul); [INFO] [stdout] | ---------------------------- in this macro invocation [INFO] [stdout] = help: consider adding an explicit import of `NativeCallContext` to disambiguate [INFO] [stdout] note: `NativeCallContext` could also refer to the struct imported here [INFO] [stdout] --> src/tree.rs:152:17 [INFO] [stdout] | [INFO] [stdout] 152 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 212 | define_binary_fns!(mul, Mul); [INFO] [stdout] | ---------------------------- in this macro invocation [INFO] [stdout] = help: consider adding an explicit import of `NativeCallContext` to disambiguate [INFO] [stdout] = note: this error originates in the macro `define_binary_fns` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `NativeCallContext` is ambiguous [INFO] [stdout] --> src/tree.rs:153:17 [INFO] [stdout] | [INFO] [stdout] 153 | use NativeCallContext; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and a macro-expanded name in the same module during import or macro resolution [INFO] [stdout] note: `NativeCallContext` could refer to the struct imported here [INFO] [stdout] --> src/tree.rs:152:17 [INFO] [stdout] | [INFO] [stdout] 152 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 213 | define_binary_fns!(div, Div); [INFO] [stdout] | ---------------------------- in this macro invocation [INFO] [stdout] = help: consider adding an explicit import of `NativeCallContext` to disambiguate [INFO] [stdout] note: `NativeCallContext` could also refer to the struct imported here [INFO] [stdout] --> src/tree.rs:152:17 [INFO] [stdout] | [INFO] [stdout] 152 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 213 | define_binary_fns!(div, Div); [INFO] [stdout] | ---------------------------- in this macro invocation [INFO] [stdout] = help: consider adding an explicit import of `NativeCallContext` to disambiguate [INFO] [stdout] = note: this error originates in the macro `define_binary_fns` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `NativeCallContext` is ambiguous [INFO] [stdout] --> src/tree.rs:153:17 [INFO] [stdout] | [INFO] [stdout] 153 | use NativeCallContext; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and a macro-expanded name in the same module during import or macro resolution [INFO] [stdout] note: `NativeCallContext` could refer to the struct imported here [INFO] [stdout] --> src/tree.rs:152:17 [INFO] [stdout] | [INFO] [stdout] 152 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 214 | define_binary_fns!(min); [INFO] [stdout] | ----------------------- in this macro invocation [INFO] [stdout] = help: consider adding an explicit import of `NativeCallContext` to disambiguate [INFO] [stdout] note: `NativeCallContext` could also refer to the struct imported here [INFO] [stdout] --> src/tree.rs:152:17 [INFO] [stdout] | [INFO] [stdout] 152 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 214 | define_binary_fns!(min); [INFO] [stdout] | ----------------------- in this macro invocation [INFO] [stdout] = help: consider adding an explicit import of `NativeCallContext` to disambiguate [INFO] [stdout] = note: this error originates in the macro `define_binary_fns` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `NativeCallContext` is ambiguous [INFO] [stdout] --> src/tree.rs:153:17 [INFO] [stdout] | [INFO] [stdout] 153 | use NativeCallContext; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and a macro-expanded name in the same module during import or macro resolution [INFO] [stdout] note: `NativeCallContext` could refer to the struct imported here [INFO] [stdout] --> src/tree.rs:152:17 [INFO] [stdout] | [INFO] [stdout] 152 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 215 | define_binary_fns!(max); [INFO] [stdout] | ----------------------- in this macro invocation [INFO] [stdout] = help: consider adding an explicit import of `NativeCallContext` to disambiguate [INFO] [stdout] note: `NativeCallContext` could also refer to the struct imported here [INFO] [stdout] --> src/tree.rs:152:17 [INFO] [stdout] | [INFO] [stdout] 152 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 215 | define_binary_fns!(max); [INFO] [stdout] | ----------------------- in this macro invocation [INFO] [stdout] = help: consider adding an explicit import of `NativeCallContext` to disambiguate [INFO] [stdout] = note: this error originates in the macro `define_binary_fns` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `NativeCallContext` is ambiguous [INFO] [stdout] --> src/tree.rs:153:17 [INFO] [stdout] | [INFO] [stdout] 153 | use NativeCallContext; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and a macro-expanded name in the same module during import or macro resolution [INFO] [stdout] note: `NativeCallContext` could refer to the struct imported here [INFO] [stdout] --> src/tree.rs:152:17 [INFO] [stdout] | [INFO] [stdout] 152 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 216 | define_binary_fns!(compare); [INFO] [stdout] | --------------------------- in this macro invocation [INFO] [stdout] = help: consider adding an explicit import of `NativeCallContext` to disambiguate [INFO] [stdout] note: `NativeCallContext` could also refer to the struct imported here [INFO] [stdout] --> src/tree.rs:152:17 [INFO] [stdout] | [INFO] [stdout] 152 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 216 | define_binary_fns!(compare); [INFO] [stdout] | --------------------------- in this macro invocation [INFO] [stdout] = help: consider adding an explicit import of `NativeCallContext` to disambiguate [INFO] [stdout] = note: this error originates in the macro `define_binary_fns` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `NativeCallContext` is ambiguous [INFO] [stdout] --> src/tree.rs:153:17 [INFO] [stdout] | [INFO] [stdout] 153 | use NativeCallContext; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and a macro-expanded name in the same module during import or macro resolution [INFO] [stdout] note: `NativeCallContext` could refer to the struct imported here [INFO] [stdout] --> src/tree.rs:152:17 [INFO] [stdout] | [INFO] [stdout] 152 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 217 | define_binary_fns!(modulo); [INFO] [stdout] | -------------------------- in this macro invocation [INFO] [stdout] = help: consider adding an explicit import of `NativeCallContext` to disambiguate [INFO] [stdout] note: `NativeCallContext` could also refer to the struct imported here [INFO] [stdout] --> src/tree.rs:152:17 [INFO] [stdout] | [INFO] [stdout] 152 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 217 | define_binary_fns!(modulo); [INFO] [stdout] | -------------------------- in this macro invocation [INFO] [stdout] = help: consider adding an explicit import of `NativeCallContext` to disambiguate [INFO] [stdout] = note: this error originates in the macro `define_binary_fns` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `NativeCallContext` is ambiguous [INFO] [stdout] --> src/tree.rs:153:17 [INFO] [stdout] | [INFO] [stdout] 153 | use NativeCallContext; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and a macro-expanded name in the same module during import or macro resolution [INFO] [stdout] note: `NativeCallContext` could refer to the struct imported here [INFO] [stdout] --> src/tree.rs:152:17 [INFO] [stdout] | [INFO] [stdout] 152 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 218 | define_binary_fns!(and); [INFO] [stdout] | ----------------------- in this macro invocation [INFO] [stdout] = help: consider adding an explicit import of `NativeCallContext` to disambiguate [INFO] [stdout] note: `NativeCallContext` could also refer to the struct imported here [INFO] [stdout] --> src/tree.rs:152:17 [INFO] [stdout] | [INFO] [stdout] 152 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 218 | define_binary_fns!(and); [INFO] [stdout] | ----------------------- in this macro invocation [INFO] [stdout] = help: consider adding an explicit import of `NativeCallContext` to disambiguate [INFO] [stdout] = note: this error originates in the macro `define_binary_fns` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `NativeCallContext` is ambiguous [INFO] [stdout] --> src/tree.rs:153:17 [INFO] [stdout] | [INFO] [stdout] 153 | use NativeCallContext; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and a macro-expanded name in the same module during import or macro resolution [INFO] [stdout] note: `NativeCallContext` could refer to the struct imported here [INFO] [stdout] --> src/tree.rs:152:17 [INFO] [stdout] | [INFO] [stdout] 152 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 219 | define_binary_fns!(or); [INFO] [stdout] | ---------------------- in this macro invocation [INFO] [stdout] = help: consider adding an explicit import of `NativeCallContext` to disambiguate [INFO] [stdout] note: `NativeCallContext` could also refer to the struct imported here [INFO] [stdout] --> src/tree.rs:152:17 [INFO] [stdout] | [INFO] [stdout] 152 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 219 | define_binary_fns!(or); [INFO] [stdout] | ---------------------- in this macro invocation [INFO] [stdout] = help: consider adding an explicit import of `NativeCallContext` to disambiguate [INFO] [stdout] = note: this error originates in the macro `define_binary_fns` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `NativeCallContext` is ambiguous [INFO] [stdout] --> src/tree.rs:153:17 [INFO] [stdout] | [INFO] [stdout] 153 | use NativeCallContext; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and a macro-expanded name in the same module during import or macro resolution [INFO] [stdout] note: `NativeCallContext` could refer to the struct imported here [INFO] [stdout] --> src/tree.rs:152:17 [INFO] [stdout] | [INFO] [stdout] 152 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 220 | define_binary_fns!(atan2); [INFO] [stdout] | ------------------------- in this macro invocation [INFO] [stdout] = help: consider adding an explicit import of `NativeCallContext` to disambiguate [INFO] [stdout] note: `NativeCallContext` could also refer to the struct imported here [INFO] [stdout] --> src/tree.rs:152:17 [INFO] [stdout] | [INFO] [stdout] 152 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 220 | define_binary_fns!(atan2); [INFO] [stdout] | ------------------------- in this macro invocation [INFO] [stdout] = help: consider adding an explicit import of `NativeCallContext` to disambiguate [INFO] [stdout] = note: this error originates in the macro `define_binary_fns` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `NativeCallContext` is ambiguous [INFO] [stdout] --> src/tree.rs:153:17 [INFO] [stdout] | [INFO] [stdout] 153 | use NativeCallContext; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and a macro-expanded name in the same module during import or macro resolution [INFO] [stdout] note: `NativeCallContext` could refer to the struct imported here [INFO] [stdout] --> src/tree.rs:152:17 [INFO] [stdout] | [INFO] [stdout] 152 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 210 | define_binary_fns!(add, Add); [INFO] [stdout] | ---------------------------- in this macro invocation [INFO] [stdout] = help: consider adding an explicit import of `NativeCallContext` to disambiguate [INFO] [stdout] note: `NativeCallContext` could also refer to the struct imported here [INFO] [stdout] --> src/tree.rs:152:17 [INFO] [stdout] | [INFO] [stdout] 152 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 210 | define_binary_fns!(add, Add); [INFO] [stdout] | ---------------------------- in this macro invocation [INFO] [stdout] = help: consider adding an explicit import of `NativeCallContext` to disambiguate [INFO] [stdout] = note: this error originates in the macro `define_binary_fns` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `NativeCallContext` is ambiguous [INFO] [stdout] --> src/tree.rs:153:17 [INFO] [stdout] | [INFO] [stdout] 153 | use NativeCallContext; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and a macro-expanded name in the same module during import or macro resolution [INFO] [stdout] note: `NativeCallContext` could refer to the struct imported here [INFO] [stdout] --> src/tree.rs:152:17 [INFO] [stdout] | [INFO] [stdout] 152 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 211 | define_binary_fns!(sub, Sub); [INFO] [stdout] | ---------------------------- in this macro invocation [INFO] [stdout] = help: consider adding an explicit import of `NativeCallContext` to disambiguate [INFO] [stdout] note: `NativeCallContext` could also refer to the struct imported here [INFO] [stdout] --> src/tree.rs:152:17 [INFO] [stdout] | [INFO] [stdout] 152 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 211 | define_binary_fns!(sub, Sub); [INFO] [stdout] | ---------------------------- in this macro invocation [INFO] [stdout] = help: consider adding an explicit import of `NativeCallContext` to disambiguate [INFO] [stdout] = note: this error originates in the macro `define_binary_fns` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `NativeCallContext` is ambiguous [INFO] [stdout] --> src/tree.rs:153:17 [INFO] [stdout] | [INFO] [stdout] 153 | use NativeCallContext; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and a macro-expanded name in the same module during import or macro resolution [INFO] [stdout] note: `NativeCallContext` could refer to the struct imported here [INFO] [stdout] --> src/tree.rs:152:17 [INFO] [stdout] | [INFO] [stdout] 152 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 212 | define_binary_fns!(mul, Mul); [INFO] [stdout] | ---------------------------- in this macro invocation [INFO] [stdout] = help: consider adding an explicit import of `NativeCallContext` to disambiguate [INFO] [stdout] note: `NativeCallContext` could also refer to the struct imported here [INFO] [stdout] --> src/tree.rs:152:17 [INFO] [stdout] | [INFO] [stdout] 152 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 212 | define_binary_fns!(mul, Mul); [INFO] [stdout] | ---------------------------- in this macro invocation [INFO] [stdout] = help: consider adding an explicit import of `NativeCallContext` to disambiguate [INFO] [stdout] = note: this error originates in the macro `define_binary_fns` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `NativeCallContext` is ambiguous [INFO] [stdout] --> src/tree.rs:153:17 [INFO] [stdout] | [INFO] [stdout] 153 | use NativeCallContext; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and a macro-expanded name in the same module during import or macro resolution [INFO] [stdout] note: `NativeCallContext` could refer to the struct imported here [INFO] [stdout] --> src/tree.rs:152:17 [INFO] [stdout] | [INFO] [stdout] 152 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 213 | define_binary_fns!(div, Div); [INFO] [stdout] | ---------------------------- in this macro invocation [INFO] [stdout] = help: consider adding an explicit import of `NativeCallContext` to disambiguate [INFO] [stdout] note: `NativeCallContext` could also refer to the struct imported here [INFO] [stdout] --> src/tree.rs:152:17 [INFO] [stdout] | [INFO] [stdout] 152 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 213 | define_binary_fns!(div, Div); [INFO] [stdout] | ---------------------------- in this macro invocation [INFO] [stdout] = help: consider adding an explicit import of `NativeCallContext` to disambiguate [INFO] [stdout] = note: this error originates in the macro `define_binary_fns` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `NativeCallContext` is ambiguous [INFO] [stdout] --> src/tree.rs:153:17 [INFO] [stdout] | [INFO] [stdout] 153 | use NativeCallContext; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and a macro-expanded name in the same module during import or macro resolution [INFO] [stdout] note: `NativeCallContext` could refer to the struct imported here [INFO] [stdout] --> src/tree.rs:152:17 [INFO] [stdout] | [INFO] [stdout] 152 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 214 | define_binary_fns!(min); [INFO] [stdout] | ----------------------- in this macro invocation [INFO] [stdout] = help: consider adding an explicit import of `NativeCallContext` to disambiguate [INFO] [stdout] note: `NativeCallContext` could also refer to the struct imported here [INFO] [stdout] --> src/tree.rs:152:17 [INFO] [stdout] | [INFO] [stdout] 152 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 214 | define_binary_fns!(min); [INFO] [stdout] | ----------------------- in this macro invocation [INFO] [stdout] = help: consider adding an explicit import of `NativeCallContext` to disambiguate [INFO] [stdout] = note: this error originates in the macro `define_binary_fns` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `NativeCallContext` is ambiguous [INFO] [stdout] --> src/tree.rs:153:17 [INFO] [stdout] | [INFO] [stdout] 153 | use NativeCallContext; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and a macro-expanded name in the same module during import or macro resolution [INFO] [stdout] note: `NativeCallContext` could refer to the struct imported here [INFO] [stdout] --> src/tree.rs:152:17 [INFO] [stdout] | [INFO] [stdout] 152 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 215 | define_binary_fns!(max); [INFO] [stdout] | ----------------------- in this macro invocation [INFO] [stdout] = help: consider adding an explicit import of `NativeCallContext` to disambiguate [INFO] [stdout] note: `NativeCallContext` could also refer to the struct imported here [INFO] [stdout] --> src/tree.rs:152:17 [INFO] [stdout] | [INFO] [stdout] 152 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 215 | define_binary_fns!(max); [INFO] [stdout] | ----------------------- in this macro invocation [INFO] [stdout] = help: consider adding an explicit import of `NativeCallContext` to disambiguate [INFO] [stdout] = note: this error originates in the macro `define_binary_fns` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `NativeCallContext` is ambiguous [INFO] [stdout] --> src/tree.rs:153:17 [INFO] [stdout] | [INFO] [stdout] 153 | use NativeCallContext; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and a macro-expanded name in the same module during import or macro resolution [INFO] [stdout] note: `NativeCallContext` could refer to the struct imported here [INFO] [stdout] --> src/tree.rs:152:17 [INFO] [stdout] | [INFO] [stdout] 152 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 216 | define_binary_fns!(compare); [INFO] [stdout] | --------------------------- in this macro invocation [INFO] [stdout] = help: consider adding an explicit import of `NativeCallContext` to disambiguate [INFO] [stdout] note: `NativeCallContext` could also refer to the struct imported here [INFO] [stdout] --> src/tree.rs:152:17 [INFO] [stdout] | [INFO] [stdout] 152 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 216 | define_binary_fns!(compare); [INFO] [stdout] | --------------------------- in this macro invocation [INFO] [stdout] = help: consider adding an explicit import of `NativeCallContext` to disambiguate [INFO] [stdout] = note: this error originates in the macro `define_binary_fns` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `NativeCallContext` is ambiguous [INFO] [stdout] --> src/tree.rs:153:17 [INFO] [stdout] | [INFO] [stdout] 153 | use NativeCallContext; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and a macro-expanded name in the same module during import or macro resolution [INFO] [stdout] note: `NativeCallContext` could refer to the struct imported here [INFO] [stdout] --> src/tree.rs:152:17 [INFO] [stdout] | [INFO] [stdout] 152 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 217 | define_binary_fns!(modulo); [INFO] [stdout] | -------------------------- in this macro invocation [INFO] [stdout] = help: consider adding an explicit import of `NativeCallContext` to disambiguate [INFO] [stdout] note: `NativeCallContext` could also refer to the struct imported here [INFO] [stdout] --> src/tree.rs:152:17 [INFO] [stdout] | [INFO] [stdout] 152 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 217 | define_binary_fns!(modulo); [INFO] [stdout] | -------------------------- in this macro invocation [INFO] [stdout] = help: consider adding an explicit import of `NativeCallContext` to disambiguate [INFO] [stdout] = note: this error originates in the macro `define_binary_fns` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `NativeCallContext` is ambiguous [INFO] [stdout] --> src/tree.rs:153:17 [INFO] [stdout] | [INFO] [stdout] 153 | use NativeCallContext; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and a macro-expanded name in the same module during import or macro resolution [INFO] [stdout] note: `NativeCallContext` could refer to the struct imported here [INFO] [stdout] --> src/tree.rs:152:17 [INFO] [stdout] | [INFO] [stdout] 152 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 218 | define_binary_fns!(and); [INFO] [stdout] | ----------------------- in this macro invocation [INFO] [stdout] = help: consider adding an explicit import of `NativeCallContext` to disambiguate [INFO] [stdout] note: `NativeCallContext` could also refer to the struct imported here [INFO] [stdout] --> src/tree.rs:152:17 [INFO] [stdout] | [INFO] [stdout] 152 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 218 | define_binary_fns!(and); [INFO] [stdout] | ----------------------- in this macro invocation [INFO] [stdout] = help: consider adding an explicit import of `NativeCallContext` to disambiguate [INFO] [stdout] = note: this error originates in the macro `define_binary_fns` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `NativeCallContext` is ambiguous [INFO] [stdout] --> src/tree.rs:153:17 [INFO] [stdout] | [INFO] [stdout] 153 | use NativeCallContext; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and a macro-expanded name in the same module during import or macro resolution [INFO] [stdout] note: `NativeCallContext` could refer to the struct imported here [INFO] [stdout] --> src/tree.rs:152:17 [INFO] [stdout] | [INFO] [stdout] 152 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 219 | define_binary_fns!(or); [INFO] [stdout] | ---------------------- in this macro invocation [INFO] [stdout] = help: consider adding an explicit import of `NativeCallContext` to disambiguate [INFO] [stdout] note: `NativeCallContext` could also refer to the struct imported here [INFO] [stdout] --> src/tree.rs:152:17 [INFO] [stdout] | [INFO] [stdout] 152 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 219 | define_binary_fns!(or); [INFO] [stdout] | ---------------------- in this macro invocation [INFO] [stdout] = help: consider adding an explicit import of `NativeCallContext` to disambiguate [INFO] [stdout] = note: this error originates in the macro `define_binary_fns` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `NativeCallContext` is ambiguous [INFO] [stdout] --> src/tree.rs:153:17 [INFO] [stdout] | [INFO] [stdout] 153 | use NativeCallContext; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and a macro-expanded name in the same module during import or macro resolution [INFO] [stdout] note: `NativeCallContext` could refer to the struct imported here [INFO] [stdout] --> src/tree.rs:152:17 [INFO] [stdout] | [INFO] [stdout] 152 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 220 | define_binary_fns!(atan2); [INFO] [stdout] | ------------------------- in this macro invocation [INFO] [stdout] = help: consider adding an explicit import of `NativeCallContext` to disambiguate [INFO] [stdout] note: `NativeCallContext` could also refer to the struct imported here [INFO] [stdout] --> src/tree.rs:152:17 [INFO] [stdout] | [INFO] [stdout] 152 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] ... [INFO] [stdout] 220 | define_binary_fns!(atan2); [INFO] [stdout] | ------------------------- in this macro invocation [INFO] [stdout] = help: consider adding an explicit import of `NativeCallContext` to disambiguate [INFO] [stdout] = note: this error originates in the macro `define_binary_fns` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] For more information about this error, try `rustc --explain E0659`. [INFO] [stdout] [INFO] [stderr] error: could not compile `fidget-rhai` (lib) due to 11 previous errors [INFO] [stderr] warning: build failed, waiting for other jobs to finish... [INFO] [stdout] For more information about this error, try `rustc --explain E0659`. [INFO] [stdout] [INFO] [stderr] error: could not compile `fidget-rhai` (lib test) due to 11 previous errors [INFO] running `Command { std: "docker" "inspect" "1f90ef71fe4eb993de4253088c1918ecd67c34915999c0dd853423d5964c3512", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "1f90ef71fe4eb993de4253088c1918ecd67c34915999c0dd853423d5964c3512", kill_on_drop: false }` [INFO] [stdout] 1f90ef71fe4eb993de4253088c1918ecd67c34915999c0dd853423d5964c3512