[INFO] fetching crate bronzedb-protocol 0.1.0... [INFO] checking bronzedb-protocol-0.1.0 against master#f609b7e0586f81fefb3523e3e17adf779ac416be for pr-129466-2 [INFO] extracting crate bronzedb-protocol 0.1.0 into /workspace/builds/worker-1-tc1/source [INFO] validating manifest of crates.io crate bronzedb-protocol 0.1.0 on toolchain f609b7e0586f81fefb3523e3e17adf779ac416be [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+f609b7e0586f81fefb3523e3e17adf779ac416be" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] started tweaking crates.io crate bronzedb-protocol 0.1.0 [INFO] finished tweaking crates.io crate bronzedb-protocol 0.1.0 [INFO] tweaked toml for crates.io crate bronzedb-protocol 0.1.0 written to /workspace/builds/worker-1-tc1/source/Cargo.toml [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+f609b7e0586f81fefb3523e3e17adf779ac416be" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Updating crates.io index [INFO] [stderr] Locking 9 packages to latest compatible versions [INFO] [stderr] Adding proc-macro2 v0.4.30 (available: v1.0.86) [INFO] [stderr] Adding quote v0.6.13 (available: v1.0.37) [INFO] [stderr] Adding syn v0.14.9 (available: v2.0.77) [INFO] [stderr] Adding unicode-xid v0.1.0 (available: v0.2.6) [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+f609b7e0586f81fefb3523e3e17adf779ac416be" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Downloading crates ... [INFO] [stderr] Downloaded speculate v0.1.2 [INFO] [stderr] Downloaded bronzedb-util v0.1.0 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-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:ceb6ea022f8a89cebbe621bb4987e73a935bd40dfbb726f832cfff4742a5b95a" "/opt/rustwide/cargo-home/bin/cargo" "+f609b7e0586f81fefb3523e3e17adf779ac416be" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] e688206b58b743fab4012a66938032f6d25e383856ca34ab0ab5f07925f43e09 [INFO] running `Command { std: "docker" "start" "-a" "e688206b58b743fab4012a66938032f6d25e383856ca34ab0ab5f07925f43e09", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "e688206b58b743fab4012a66938032f6d25e383856ca34ab0ab5f07925f43e09", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "e688206b58b743fab4012a66938032f6d25e383856ca34ab0ab5f07925f43e09", kill_on_drop: false }` [INFO] [stdout] e688206b58b743fab4012a66938032f6d25e383856ca34ab0ab5f07925f43e09 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-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:ceb6ea022f8a89cebbe621bb4987e73a935bd40dfbb726f832cfff4742a5b95a" "/opt/rustwide/cargo-home/bin/cargo" "+f609b7e0586f81fefb3523e3e17adf779ac416be" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] 1caf6c726da91356c633b1fffb8709b0782a9f94343c9e828113825b7448ebef [INFO] running `Command { std: "docker" "start" "-a" "1caf6c726da91356c633b1fffb8709b0782a9f94343c9e828113825b7448ebef", kill_on_drop: false }` [INFO] [stderr] Compiling proc-macro2 v0.4.30 [INFO] [stderr] Compiling unicode-xid v0.1.0 [INFO] [stderr] Checking bronzedb-util v0.1.0 [INFO] [stderr] Checking bronzedb-protocol v0.1.0 (/opt/rustwide/workdir) [INFO] [stderr] Compiling quote v0.6.13 [INFO] [stderr] Compiling syn v0.14.9 [INFO] [stderr] Compiling speculate v0.1.2 [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:152:21 [INFO] [stdout] | [INFO] [stdout] 152 | assert!(matches!(&new_request, Request::Delete(ref _key))); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 162 | assert_delete!(b"name"); [INFO] [stdout] | ----------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:160:18 [INFO] [stdout] | [INFO] [stdout] 160 | describe "delete" { [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_delete` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:152:21 [INFO] [stdout] | [INFO] [stdout] 152 | assert!(matches!(&new_request, Request::Delete(ref _key))); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 166 | assert_delete!([0; 0]); [INFO] [stdout] | ---------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:160:18 [INFO] [stdout] | [INFO] [stdout] 160 | describe "delete" { [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_delete` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:152:21 [INFO] [stdout] | [INFO] [stdout] 152 | assert!(matches!(&new_request, Request::Delete(ref _key))); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 170 | assert_delete!([0; MAX_KEY_LEN]); [INFO] [stdout] | -------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:160:18 [INFO] [stdout] | [INFO] [stdout] 160 | describe "delete" { [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_delete` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:152:21 [INFO] [stdout] | [INFO] [stdout] 152 | assert!(matches!(&new_request, Request::Delete(ref _key))); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 175 | assert_delete!([0; MAX_KEY_LEN + 1]); [INFO] [stdout] | ------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:160:18 [INFO] [stdout] | [INFO] [stdout] 160 | describe "delete" { [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_delete` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:186:21 [INFO] [stdout] | [INFO] [stdout] 186 | assert!(matches!(&new_request, Request::Get(ref _key))); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 196 | assert_get!(b"name"); [INFO] [stdout] | -------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:194:18 [INFO] [stdout] | [INFO] [stdout] 194 | describe "get" { [INFO] [stdout] | ^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_get` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:186:21 [INFO] [stdout] | [INFO] [stdout] 186 | assert!(matches!(&new_request, Request::Get(ref _key))); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 200 | assert_get!([0; 0]); [INFO] [stdout] | ------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:194:18 [INFO] [stdout] | [INFO] [stdout] 194 | describe "get" { [INFO] [stdout] | ^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_get` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:186:21 [INFO] [stdout] | [INFO] [stdout] 186 | assert!(matches!(&new_request, Request::Get(ref _key))); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 204 | assert_get!([0; MAX_KEY_LEN]); [INFO] [stdout] | ----------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:194:18 [INFO] [stdout] | [INFO] [stdout] 194 | describe "get" { [INFO] [stdout] | ^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_get` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:186:21 [INFO] [stdout] | [INFO] [stdout] 186 | assert!(matches!(&new_request, Request::Get(ref _key))); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 209 | assert_get!([0; MAX_KEY_LEN + 1]); [INFO] [stdout] | --------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:194:18 [INFO] [stdout] | [INFO] [stdout] 194 | describe "get" { [INFO] [stdout] | ^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_get` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:218:21 [INFO] [stdout] | [INFO] [stdout] 218 | assert!(matches!(new_request, Request::NoResponse)); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 224 | assert_no_response!(); [INFO] [stdout] | --------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:222:5 [INFO] [stdout] | [INFO] [stdout] 222 | / speculate! { [INFO] [stdout] 223 | | it "just no response" { [INFO] [stdout] 224 | | assert_no_response!(); [INFO] [stdout] 225 | | } [INFO] [stdout] 226 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_no_response` which comes from the expansion of the macro `speculate` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:232:21 [INFO] [stdout] | [INFO] [stdout] 232 | assert!(matches!(new_request, Request::Ping)); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 238 | assert_ping!(); [INFO] [stdout] | -------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:236:5 [INFO] [stdout] | [INFO] [stdout] 236 | / speculate! { [INFO] [stdout] 237 | | it "just ping" { [INFO] [stdout] 238 | | assert_ping!(); [INFO] [stdout] 239 | | } [INFO] [stdout] 240 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_ping` which comes from the expansion of the macro `speculate` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:270:21 [INFO] [stdout] | [INFO] [stdout] 270 | assert!(matches!(&new_request, Request::Scan{lower_bound: _, upper_bound: _})); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 330 | assert_scan!(b"last_name", b"name"); [INFO] [stdout] | ----------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:328:18 [INFO] [stdout] | [INFO] [stdout] 328 | describe "scan with two bounds" { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_scan` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:276:25 [INFO] [stdout] | [INFO] [stdout] 276 | assert!(matches!(lower_bound, Some(ref _key))); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 330 | assert_scan!(b"last_name", b"name"); [INFO] [stdout] | ----------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:328:18 [INFO] [stdout] | [INFO] [stdout] 328 | describe "scan with two bounds" { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_scan` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:277:25 [INFO] [stdout] | [INFO] [stdout] 277 | assert!(matches!(upper_bound, Some(ref _key))); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 330 | assert_scan!(b"last_name", b"name"); [INFO] [stdout] | ----------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:328:18 [INFO] [stdout] | [INFO] [stdout] 328 | describe "scan with two bounds" { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_scan` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:270:21 [INFO] [stdout] | [INFO] [stdout] 270 | assert!(matches!(&new_request, Request::Scan{lower_bound: _, upper_bound: _})); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 334 | assert_scan!([1; MAX_KEY_LEN], [MAX - 1; MAX_KEY_LEN]); [INFO] [stdout] | ------------------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:328:18 [INFO] [stdout] | [INFO] [stdout] 328 | describe "scan with two bounds" { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_scan` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:276:25 [INFO] [stdout] | [INFO] [stdout] 276 | assert!(matches!(lower_bound, Some(ref _key))); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 334 | assert_scan!([1; MAX_KEY_LEN], [MAX - 1; MAX_KEY_LEN]); [INFO] [stdout] | ------------------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:328:18 [INFO] [stdout] | [INFO] [stdout] 328 | describe "scan with two bounds" { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_scan` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:277:25 [INFO] [stdout] | [INFO] [stdout] 277 | assert!(matches!(upper_bound, Some(ref _key))); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 334 | assert_scan!([1; MAX_KEY_LEN], [MAX - 1; MAX_KEY_LEN]); [INFO] [stdout] | ------------------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:328:18 [INFO] [stdout] | [INFO] [stdout] 328 | describe "scan with two bounds" { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_scan` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:270:21 [INFO] [stdout] | [INFO] [stdout] 270 | assert!(matches!(&new_request, Request::Scan{lower_bound: _, upper_bound: _})); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 339 | assert_scan!(b"", [MAX; MAX_KEY_LEN]); [INFO] [stdout] | ------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:328:18 [INFO] [stdout] | [INFO] [stdout] 328 | describe "scan with two bounds" { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_scan` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:276:25 [INFO] [stdout] | [INFO] [stdout] 276 | assert!(matches!(lower_bound, Some(ref _key))); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 339 | assert_scan!(b"", [MAX; MAX_KEY_LEN]); [INFO] [stdout] | ------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:328:18 [INFO] [stdout] | [INFO] [stdout] 328 | describe "scan with two bounds" { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_scan` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:277:25 [INFO] [stdout] | [INFO] [stdout] 277 | assert!(matches!(upper_bound, Some(ref _key))); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 339 | assert_scan!(b"", [MAX; MAX_KEY_LEN]); [INFO] [stdout] | ------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:328:18 [INFO] [stdout] | [INFO] [stdout] 328 | describe "scan with two bounds" { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_scan` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:270:21 [INFO] [stdout] | [INFO] [stdout] 270 | assert!(matches!(&new_request, Request::Scan{lower_bound: _, upper_bound: _})); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 344 | assert_scan!([0; MAX_KEY_LEN + 1], [MAX; MAX_KEY_LEN + 1]); [INFO] [stdout] | ---------------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:328:18 [INFO] [stdout] | [INFO] [stdout] 328 | describe "scan with two bounds" { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_scan` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:276:25 [INFO] [stdout] | [INFO] [stdout] 276 | assert!(matches!(lower_bound, Some(ref _key))); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 344 | assert_scan!([0; MAX_KEY_LEN + 1], [MAX; MAX_KEY_LEN + 1]); [INFO] [stdout] | ---------------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:328:18 [INFO] [stdout] | [INFO] [stdout] 328 | describe "scan with two bounds" { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_scan` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:277:25 [INFO] [stdout] | [INFO] [stdout] 277 | assert!(matches!(upper_bound, Some(ref _key))); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 344 | assert_scan!([0; MAX_KEY_LEN + 1], [MAX; MAX_KEY_LEN + 1]); [INFO] [stdout] | ---------------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:328:18 [INFO] [stdout] | [INFO] [stdout] 328 | describe "scan with two bounds" { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_scan` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:292:25 [INFO] [stdout] | [INFO] [stdout] 292 | assert!(matches!(&new_request, Request::Scan{lower_bound: _, upper_bound: _})); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 350 | assert_scan!(b"last_name"); [INFO] [stdout] | -------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:348:18 [INFO] [stdout] | [INFO] [stdout] 348 | describe "scan with one bound" { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_scan` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:298:29 [INFO] [stdout] | [INFO] [stdout] 298 | assert!(matches!(lower_bound, Some(ref _key))); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 350 | assert_scan!(b"last_name"); [INFO] [stdout] | -------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:348:18 [INFO] [stdout] | [INFO] [stdout] 348 | describe "scan with one bound" { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_scan` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:299:29 [INFO] [stdout] | [INFO] [stdout] 299 | assert!(matches!(upper_bound, None)); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 350 | assert_scan!(b"last_name"); [INFO] [stdout] | -------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:348:18 [INFO] [stdout] | [INFO] [stdout] 348 | describe "scan with one bound" { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_scan` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:311:25 [INFO] [stdout] | [INFO] [stdout] 311 | assert!(matches!(&new_request, Request::Scan{lower_bound: _, upper_bound: _})); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 350 | assert_scan!(b"last_name"); [INFO] [stdout] | -------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:348:18 [INFO] [stdout] | [INFO] [stdout] 348 | describe "scan with one bound" { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_scan` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:317:29 [INFO] [stdout] | [INFO] [stdout] 317 | assert!(matches!(lower_bound, None)); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 350 | assert_scan!(b"last_name"); [INFO] [stdout] | -------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:348:18 [INFO] [stdout] | [INFO] [stdout] 348 | describe "scan with one bound" { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_scan` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:318:29 [INFO] [stdout] | [INFO] [stdout] 318 | assert!(matches!(upper_bound, Some(ref _key))); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 350 | assert_scan!(b"last_name"); [INFO] [stdout] | -------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:348:18 [INFO] [stdout] | [INFO] [stdout] 348 | describe "scan with one bound" { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_scan` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:292:25 [INFO] [stdout] | [INFO] [stdout] 292 | assert!(matches!(&new_request, Request::Scan{lower_bound: _, upper_bound: _})); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 354 | assert_scan!([1; MAX_KEY_LEN]); [INFO] [stdout] | ------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:348:18 [INFO] [stdout] | [INFO] [stdout] 348 | describe "scan with one bound" { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_scan` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:298:29 [INFO] [stdout] | [INFO] [stdout] 298 | assert!(matches!(lower_bound, Some(ref _key))); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 354 | assert_scan!([1; MAX_KEY_LEN]); [INFO] [stdout] | ------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:348:18 [INFO] [stdout] | [INFO] [stdout] 348 | describe "scan with one bound" { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_scan` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:299:29 [INFO] [stdout] | [INFO] [stdout] 299 | assert!(matches!(upper_bound, None)); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 354 | assert_scan!([1; MAX_KEY_LEN]); [INFO] [stdout] | ------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:348:18 [INFO] [stdout] | [INFO] [stdout] 348 | describe "scan with one bound" { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_scan` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:311:25 [INFO] [stdout] | [INFO] [stdout] 311 | assert!(matches!(&new_request, Request::Scan{lower_bound: _, upper_bound: _})); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 354 | assert_scan!([1; MAX_KEY_LEN]); [INFO] [stdout] | ------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:348:18 [INFO] [stdout] | [INFO] [stdout] 348 | describe "scan with one bound" { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_scan` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:317:29 [INFO] [stdout] | [INFO] [stdout] 317 | assert!(matches!(lower_bound, None)); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 354 | assert_scan!([1; MAX_KEY_LEN]); [INFO] [stdout] | ------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:348:18 [INFO] [stdout] | [INFO] [stdout] 348 | describe "scan with one bound" { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_scan` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:318:29 [INFO] [stdout] | [INFO] [stdout] 318 | assert!(matches!(upper_bound, Some(ref _key))); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 354 | assert_scan!([1; MAX_KEY_LEN]); [INFO] [stdout] | ------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:348:18 [INFO] [stdout] | [INFO] [stdout] 348 | describe "scan with one bound" { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_scan` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:292:25 [INFO] [stdout] | [INFO] [stdout] 292 | assert!(matches!(&new_request, Request::Scan{lower_bound: _, upper_bound: _})); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 359 | assert_scan!(b""); [INFO] [stdout] | ----------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:348:18 [INFO] [stdout] | [INFO] [stdout] 348 | describe "scan with one bound" { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_scan` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:298:29 [INFO] [stdout] | [INFO] [stdout] 298 | assert!(matches!(lower_bound, Some(ref _key))); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 359 | assert_scan!(b""); [INFO] [stdout] | ----------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:348:18 [INFO] [stdout] | [INFO] [stdout] 348 | describe "scan with one bound" { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_scan` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:299:29 [INFO] [stdout] | [INFO] [stdout] 299 | assert!(matches!(upper_bound, None)); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 359 | assert_scan!(b""); [INFO] [stdout] | ----------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:348:18 [INFO] [stdout] | [INFO] [stdout] 348 | describe "scan with one bound" { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_scan` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:311:25 [INFO] [stdout] | [INFO] [stdout] 311 | assert!(matches!(&new_request, Request::Scan{lower_bound: _, upper_bound: _})); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 359 | assert_scan!(b""); [INFO] [stdout] | ----------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:348:18 [INFO] [stdout] | [INFO] [stdout] 348 | describe "scan with one bound" { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_scan` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:317:29 [INFO] [stdout] | [INFO] [stdout] 317 | assert!(matches!(lower_bound, None)); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 359 | assert_scan!(b""); [INFO] [stdout] | ----------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:348:18 [INFO] [stdout] | [INFO] [stdout] 348 | describe "scan with one bound" { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_scan` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:318:29 [INFO] [stdout] | [INFO] [stdout] 318 | assert!(matches!(upper_bound, Some(ref _key))); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 359 | assert_scan!(b""); [INFO] [stdout] | ----------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:348:18 [INFO] [stdout] | [INFO] [stdout] 348 | describe "scan with one bound" { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_scan` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:292:25 [INFO] [stdout] | [INFO] [stdout] 292 | assert!(matches!(&new_request, Request::Scan{lower_bound: _, upper_bound: _})); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 364 | assert_scan!([MAX; MAX_KEY_LEN]); [INFO] [stdout] | -------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:348:18 [INFO] [stdout] | [INFO] [stdout] 348 | describe "scan with one bound" { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_scan` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:298:29 [INFO] [stdout] | [INFO] [stdout] 298 | assert!(matches!(lower_bound, Some(ref _key))); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 364 | assert_scan!([MAX; MAX_KEY_LEN]); [INFO] [stdout] | -------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:348:18 [INFO] [stdout] | [INFO] [stdout] 348 | describe "scan with one bound" { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_scan` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:299:29 [INFO] [stdout] | [INFO] [stdout] 299 | assert!(matches!(upper_bound, None)); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 364 | assert_scan!([MAX; MAX_KEY_LEN]); [INFO] [stdout] | -------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:348:18 [INFO] [stdout] | [INFO] [stdout] 348 | describe "scan with one bound" { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_scan` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:311:25 [INFO] [stdout] | [INFO] [stdout] 311 | assert!(matches!(&new_request, Request::Scan{lower_bound: _, upper_bound: _})); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 364 | assert_scan!([MAX; MAX_KEY_LEN]); [INFO] [stdout] | -------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:348:18 [INFO] [stdout] | [INFO] [stdout] 348 | describe "scan with one bound" { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_scan` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:317:29 [INFO] [stdout] | [INFO] [stdout] 317 | assert!(matches!(lower_bound, None)); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 364 | assert_scan!([MAX; MAX_KEY_LEN]); [INFO] [stdout] | -------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:348:18 [INFO] [stdout] | [INFO] [stdout] 348 | describe "scan with one bound" { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_scan` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:318:29 [INFO] [stdout] | [INFO] [stdout] 318 | assert!(matches!(upper_bound, Some(ref _key))); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 364 | assert_scan!([MAX; MAX_KEY_LEN]); [INFO] [stdout] | -------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:348:18 [INFO] [stdout] | [INFO] [stdout] 348 | describe "scan with one bound" { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_scan` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:292:25 [INFO] [stdout] | [INFO] [stdout] 292 | assert!(matches!(&new_request, Request::Scan{lower_bound: _, upper_bound: _})); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 369 | assert_scan!([0; MAX_KEY_LEN + 1]); [INFO] [stdout] | ---------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:348:18 [INFO] [stdout] | [INFO] [stdout] 348 | describe "scan with one bound" { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_scan` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:298:29 [INFO] [stdout] | [INFO] [stdout] 298 | assert!(matches!(lower_bound, Some(ref _key))); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 369 | assert_scan!([0; MAX_KEY_LEN + 1]); [INFO] [stdout] | ---------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:348:18 [INFO] [stdout] | [INFO] [stdout] 348 | describe "scan with one bound" { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_scan` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:299:29 [INFO] [stdout] | [INFO] [stdout] 299 | assert!(matches!(upper_bound, None)); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 369 | assert_scan!([0; MAX_KEY_LEN + 1]); [INFO] [stdout] | ---------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:348:18 [INFO] [stdout] | [INFO] [stdout] 348 | describe "scan with one bound" { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_scan` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:311:25 [INFO] [stdout] | [INFO] [stdout] 311 | assert!(matches!(&new_request, Request::Scan{lower_bound: _, upper_bound: _})); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 369 | assert_scan!([0; MAX_KEY_LEN + 1]); [INFO] [stdout] | ---------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:348:18 [INFO] [stdout] | [INFO] [stdout] 348 | describe "scan with one bound" { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_scan` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:317:29 [INFO] [stdout] | [INFO] [stdout] 317 | assert!(matches!(lower_bound, None)); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 369 | assert_scan!([0; MAX_KEY_LEN + 1]); [INFO] [stdout] | ---------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:348:18 [INFO] [stdout] | [INFO] [stdout] 348 | describe "scan with one bound" { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_scan` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:318:29 [INFO] [stdout] | [INFO] [stdout] 318 | assert!(matches!(upper_bound, Some(ref _key))); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 369 | assert_scan!([0; MAX_KEY_LEN + 1]); [INFO] [stdout] | ---------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:348:18 [INFO] [stdout] | [INFO] [stdout] 348 | describe "scan with one bound" { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_scan` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:251:21 [INFO] [stdout] | [INFO] [stdout] 251 | assert!(matches!(&new_request, Request::Scan{lower_bound: _, upper_bound: _})); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 375 | assert_scan!(); [INFO] [stdout] | -------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:373:18 [INFO] [stdout] | [INFO] [stdout] 373 | describe "scan with no bound" { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_scan` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:257:25 [INFO] [stdout] | [INFO] [stdout] 257 | assert!(matches!(lower_bound, None)); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 375 | assert_scan!(); [INFO] [stdout] | -------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:373:18 [INFO] [stdout] | [INFO] [stdout] 373 | describe "scan with no bound" { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_scan` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:258:25 [INFO] [stdout] | [INFO] [stdout] 258 | assert!(matches!(upper_bound, None)); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 375 | assert_scan!(); [INFO] [stdout] | -------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:373:18 [INFO] [stdout] | [INFO] [stdout] 373 | describe "scan with no bound" { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_scan` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:387:21 [INFO] [stdout] | [INFO] [stdout] 387 | assert!(matches!(&new_request, Request::Set(ref _key, ref _value))); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 398 | assert_set!(b"name", b"hexi"); [INFO] [stdout] | ----------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:396:18 [INFO] [stdout] | [INFO] [stdout] 396 | describe "set" { [INFO] [stdout] | ^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_set` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:387:21 [INFO] [stdout] | [INFO] [stdout] 387 | assert!(matches!(&new_request, Request::Set(ref _key, ref _value))); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 402 | assert_set!([0; 0], [0; 0]); [INFO] [stdout] | --------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:396:18 [INFO] [stdout] | [INFO] [stdout] 396 | describe "set" { [INFO] [stdout] | ^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_set` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:387:21 [INFO] [stdout] | [INFO] [stdout] 387 | assert!(matches!(&new_request, Request::Set(ref _key, ref _value))); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 406 | assert_set!([0; MAX_KEY_LEN], [0; MAX_VALUE_LEN]); [INFO] [stdout] | ------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:396:18 [INFO] [stdout] | [INFO] [stdout] 396 | describe "set" { [INFO] [stdout] | ^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_set` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:387:21 [INFO] [stdout] | [INFO] [stdout] 387 | assert!(matches!(&new_request, Request::Set(ref _key, ref _value))); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 411 | assert_set!([0; MAX_KEY_LEN + 1], [0; MAX_VALUE_LEN]); [INFO] [stdout] | ----------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:396:18 [INFO] [stdout] | [INFO] [stdout] 396 | describe "set" { [INFO] [stdout] | ^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_set` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/request.rs:387:21 [INFO] [stdout] | [INFO] [stdout] 387 | assert!(matches!(&new_request, Request::Set(ref _key, ref _value))); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 416 | assert_set!([0; MAX_KEY_LEN], [0; MAX_VALUE_LEN + 1]); [INFO] [stdout] | ----------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/request.rs:396:18 [INFO] [stdout] | [INFO] [stdout] 396 | describe "set" { [INFO] [stdout] | ^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_set` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/response.rs:141:21 [INFO] [stdout] | [INFO] [stdout] 141 | assert!(matches!(new_resp, Status(ref _x))); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 151 | assert_status_not_ok!(IOError); [INFO] [stdout] | ------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/response.rs:149:18 [INFO] [stdout] | [INFO] [stdout] 149 | describe "status not ok" { [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_status_not_ok` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/response.rs:141:21 [INFO] [stdout] | [INFO] [stdout] 141 | assert!(matches!(new_resp, Status(ref _x))); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 155 | assert_status_not_ok!(UnknownAction); [INFO] [stdout] | ------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/response.rs:149:18 [INFO] [stdout] | [INFO] [stdout] 149 | describe "status not ok" { [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_status_not_ok` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/response.rs:141:21 [INFO] [stdout] | [INFO] [stdout] 141 | assert!(matches!(new_resp, Status(ref _x))); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 159 | assert_status_not_ok!(EngineError); [INFO] [stdout] | ---------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/response.rs:149:18 [INFO] [stdout] | [INFO] [stdout] 149 | describe "status not ok" { [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_status_not_ok` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/response.rs:141:21 [INFO] [stdout] | [INFO] [stdout] 141 | assert!(matches!(new_resp, Status(ref _x))); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 163 | assert_status_not_ok!(NotFound); [INFO] [stdout] | ------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/response.rs:149:18 [INFO] [stdout] | [INFO] [stdout] 149 | describe "status not ok" { [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_status_not_ok` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/response.rs:194:21 [INFO] [stdout] | [INFO] [stdout] 194 | assert!(matches!(new_resp, SingleValue(_))); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 204 | assert_get_ok!(b"Hexi"); [INFO] [stdout] | ----------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/response.rs:202:18 [INFO] [stdout] | [INFO] [stdout] 202 | describe "get ok" { [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_get_ok` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/response.rs:194:21 [INFO] [stdout] | [INFO] [stdout] 194 | assert!(matches!(new_resp, SingleValue(_))); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 208 | assert_get_ok!([0; 0]); [INFO] [stdout] | ---------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/response.rs:202:18 [INFO] [stdout] | [INFO] [stdout] 202 | describe "get ok" { [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_get_ok` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/response.rs:194:21 [INFO] [stdout] | [INFO] [stdout] 194 | assert!(matches!(new_resp, SingleValue(_))); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 212 | assert_get_ok!([0; MAX_VALUE_LEN]); [INFO] [stdout] | ---------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/response.rs:202:18 [INFO] [stdout] | [INFO] [stdout] 202 | describe "get ok" { [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_get_ok` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `matches` is ambiguous [INFO] [stdout] --> src/response.rs:194:21 [INFO] [stdout] | [INFO] [stdout] 194 | assert!(matches!(new_resp, SingleValue(_))); [INFO] [stdout] | ^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 217 | assert_get_ok!([0; MAX_VALUE_LEN + 1]); [INFO] [stdout] | -------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution [INFO] [stdout] = note: `matches` could refer to a macro from prelude [INFO] [stdout] note: `matches` could also refer to the macro imported here [INFO] [stdout] --> src/response.rs:202:18 [INFO] [stdout] | [INFO] [stdout] 202 | describe "get ok" { [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `matches` to disambiguate [INFO] [stdout] = help: or use `self::matches` to refer to this macro unambiguously [INFO] [stdout] = note: this error originates in the macro `assert_get_ok` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: aborting due to 68 previous errors [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] For more information about this error, try `rustc --explain E0659`. [INFO] [stdout] [INFO] [stderr] error: could not compile `bronzedb-protocol` (lib test) due to 69 previous errors [INFO] running `Command { std: "docker" "inspect" "1caf6c726da91356c633b1fffb8709b0782a9f94343c9e828113825b7448ebef", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "1caf6c726da91356c633b1fffb8709b0782a9f94343c9e828113825b7448ebef", kill_on_drop: false }` [INFO] [stdout] 1caf6c726da91356c633b1fffb8709b0782a9f94343c9e828113825b7448ebef