[INFO] fetching crate sertyp 0.1.5...
[INFO] checking sertyp-0.1.5 against 52995a223f2919dd3e2e427231db90a257350ded for pr-129249-4
[INFO] extracting crate sertyp 0.1.5 into /workspace/builds/worker-2-tc2/source
[INFO] started tweaking crates.io crate sertyp 0.1.5
[INFO] finished tweaking crates.io crate sertyp 0.1.5
[INFO] tweaked toml for crates.io crate sertyp 0.1.5 written to /workspace/builds/worker-2-tc2/source/Cargo.toml
[INFO] validating manifest of crates.io crate sertyp 0.1.5 on toolchain 52995a223f2919dd3e2e427231db90a257350ded
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+52995a223f2919dd3e2e427231db90a257350ded" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] crate crates.io crate sertyp 0.1.5 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" "+52995a223f2919dd3e2e427231db90a257350ded" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/target:/opt/rustwide/target:rw,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" "-m" "1610612736" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:c0af3998e971868164375a7dfb646c9933ddd1a3bdb00fa2041266763dc1eeab" "sleep" "infinity", kill_on_drop: false }`
[INFO] [stdout] 2e46f8b572e6cde59b0d172db8289ac9003a59bbf61f76ab4faf9117ca26ad77
[INFO] running `Command { std: "docker" "start" "2e46f8b572e6cde59b0d172db8289ac9003a59bbf61f76ab4faf9117ca26ad77", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "2e46f8b572e6cde59b0d172db8289ac9003a59bbf61f76ab4faf9117ca26ad77", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "exec" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-w" "/opt/rustwide/workdir" "--user" "0:0" "2e46f8b572e6cde59b0d172db8289ac9003a59bbf61f76ab4faf9117ca26ad77" "/opt/rustwide/cargo-home/bin/cargo" "+52995a223f2919dd3e2e427231db90a257350ded" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "2e46f8b572e6cde59b0d172db8289ac9003a59bbf61f76ab4faf9117ca26ad77", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "exec" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-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" "-w" "/opt/rustwide/workdir" "--user" "0:0" "2e46f8b572e6cde59b0d172db8289ac9003a59bbf61f76ab4faf9117ca26ad77" "/opt/rustwide/cargo-home/bin/cargo" "+52995a223f2919dd3e2e427231db90a257350ded" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }`
[INFO] [stderr]    Compiling find-msvc-tools v0.1.9
[INFO] [stderr]    Compiling object v0.37.3
[INFO] [stderr]    Compiling memchr v2.7.6
[INFO] [stderr]    Compiling libc v0.2.186
[INFO] [stderr]    Compiling unicode-segmentation v1.13.2
[INFO] [stderr]    Compiling paste v1.0.15
[INFO] [stderr]    Compiling zmij v1.0.18
[INFO] [stderr]    Compiling unicode-xid v0.2.6
[INFO] [stderr]     Checking allocator-api2 v0.2.21
[INFO] [stderr]     Checking foldhash v0.1.5
[INFO] [stderr]    Compiling syn v2.0.114
[INFO] [stderr]    Compiling num-traits v0.2.19
[INFO] [stderr]     Checking half v1.8.3
[INFO] [stderr]     Checking unicode-ident v1.0.22
[INFO] [stderr]    Compiling serde_json v1.0.150
[INFO] [stderr]     Checking rangemap v1.7.1
[INFO] [stderr]    Compiling cc v1.2.62
[INFO] [stderr]     Checking hashbrown v0.15.5
[INFO] [stderr]    Compiling convert_case v0.10.0
[INFO] [stderr]    Compiling stacker v0.1.24
[INFO] [stderr]    Compiling serde_derive v1.0.228
[INFO] [stderr]    Compiling derive_more-impl v2.1.1
[INFO] [stderr]    Compiling sertyp_macros v0.1.5
[INFO] [stderr]    Compiling ar_archive_writer v0.5.1
[INFO] [stderr]    Compiling psm v0.1.31
[INFO] [stderr]     Checking chumsky v0.13.0
[INFO] [stderr]     Checking serde v1.0.228
[INFO] [stderr]     Checking serde_cbor v0.11.2
[INFO] [stderr]     Checking derive_more v2.1.1
[INFO] [stderr]     Checking sertyp v0.1.5 (/opt/rustwide/workdir)
[INFO] [stdout] error: useless conversion to the same type: `S`
[INFO] [stdout]   --> src/types/content/sequence/error.rs:51:41
[INFO] [stdout]    |
[INFO] [stdout] 51 |         move |span: S| TypstError::full(span.into(), label.into(), expected.into(), found.into())
[INFO] [stdout]    |                                         ^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: this method call relies on the `impl<T> Into<T> for T` blanket implementation and type inference, which is a semver hazard as a new `impl Into<_>` that affects your type might be added in the future causing type inference errors
[INFO] [stdout]    = note: `#[deny(self_type_conversion)]` on by default
[INFO] [stdout] help: consider removing the conversion call
[INFO] [stdout]    |
[INFO] [stdout] 51 -         move |span: S| TypstError::full(span.into(), label.into(), expected.into(), found.into())
[INFO] [stdout] 51 +         move |span: S| TypstError::full(span, label.into(), expected.into(), found.into())
[INFO] [stdout]    |
[INFO] [stdout] help: you can use the fully-qualified path to avoid triggering this lint
[INFO] [stdout]    |
[INFO] [stdout] 51 -         move |span: S| TypstError::full(span.into(), label.into(), expected.into(), found.into())
[INFO] [stdout] 51 +         move |span: S| TypstError::full(<S as Into<_>>::into(span), label.into(), expected.into(), found.into())
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: useless conversion to the same type: `TypstError<'_>`
[INFO] [stdout]    --> src/types/content/sequence/chumsky/parser.rs:401:40
[INFO] [stdout]     |
[INFO] [stdout] 392 |                   macro_rules! field {
[INFO] [stdout] ...
[INFO] [stdout] 401 |                                   return TypstError::full(
[INFO] [stdout]     |  ________________________________________^
[INFO] [stdout] 402 | |                                     span,
[INFO] [stdout] 403 | |                                     "Invalid Variable Subscript/Superscript",
[INFO] [stdout] 404 | |                                     "Variable like declaration in attachment",
[INFO] [stdout] ...   |
[INFO] [stdout] 411 | |                                 .into();
[INFO] [stdout]     | |_______________________________________^
[INFO] [stdout] ...
[INFO] [stdout] 424 |                   field!(&**attach.base, true)?;
[INFO] [stdout]     |                   ---------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this method call relies on the `impl<T> Into<T> for T` blanket implementation and type inference, which is a semver hazard as a new `impl Into<_>` that affects your type might be added in the future causing type inference errors
[INFO] [stdout]     = note: you can instead use the fully-qualified path `<TypstError<'_> as Into<TypstError<'_>>::into(val) to avoid triggering this lint
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: useless conversion to the same type: `TypstError<'_>`
[INFO] [stdout]    --> src/types/content/sequence/chumsky/parser.rs:401:40
[INFO] [stdout]     |
[INFO] [stdout] 392 | /                  macro_rules! field {
[INFO] [stdout] 393 | |                      ($field:expr, $canonical:expr) => {{
[INFO] [stdout] 394 | |                          variable::<LocatingSequence<'this, 'data>, E>($canonical)
[INFO] [stdout] 395 | |                              .parse(<LocatingSequence as From<&'this Content<'data>>>::from(
[INFO] [stdout] ...   |
[INFO] [stdout] 401 | |                                  return TypstError::full(
[INFO] [stdout]     | | ________________________________________^
[INFO] [stdout] 402 | ||                                     span,
[INFO] [stdout] 403 | ||                                     "Invalid Variable Subscript/Superscript",
[INFO] [stdout] 404 | ||                                     "Variable like declaration in attachment",
[INFO] [stdout] ...   ||
[INFO] [stdout] 411 | ||                                 .into();
[INFO] [stdout]     | ||_______________________________________^
[INFO] [stdout] 412 | |                              })
[INFO] [stdout] 413 | |                      }};
[INFO] [stdout] 414 | |                  }
[INFO] [stdout]     | |__________________- this error originates in the macro `field` which comes from the expansion of the macro `maybe_field`
[INFO] [stdout] ...
[INFO] [stdout] 425 |                    maybe_field!(&attach.b, false)?;
[INFO] [stdout]     |                    ------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this method call relies on the `impl<T> Into<T> for T` blanket implementation and type inference, which is a semver hazard as a new `impl Into<_>` that affects your type might be added in the future causing type inference errors
[INFO] [stdout]     = note: you can instead use the fully-qualified path `<TypstError<'_> as Into<TypstError<'_>>::into(val) to avoid triggering this lint
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: useless conversion to the same type: `TypstError<'_>`
[INFO] [stdout]    --> src/types/content/sequence/chumsky/parser.rs:401:40
[INFO] [stdout]     |
[INFO] [stdout] 392 | /                  macro_rules! field {
[INFO] [stdout] 393 | |                      ($field:expr, $canonical:expr) => {{
[INFO] [stdout] 394 | |                          variable::<LocatingSequence<'this, 'data>, E>($canonical)
[INFO] [stdout] 395 | |                              .parse(<LocatingSequence as From<&'this Content<'data>>>::from(
[INFO] [stdout] ...   |
[INFO] [stdout] 401 | |                                  return TypstError::full(
[INFO] [stdout]     | | ________________________________________^
[INFO] [stdout] 402 | ||                                     span,
[INFO] [stdout] 403 | ||                                     "Invalid Variable Subscript/Superscript",
[INFO] [stdout] 404 | ||                                     "Variable like declaration in attachment",
[INFO] [stdout] ...   ||
[INFO] [stdout] 411 | ||                                 .into();
[INFO] [stdout]     | ||_______________________________________^
[INFO] [stdout] 412 | |                              })
[INFO] [stdout] 413 | |                      }};
[INFO] [stdout] 414 | |                  }
[INFO] [stdout]     | |__________________- this error originates in the macro `field` which comes from the expansion of the macro `maybe_field`
[INFO] [stdout] ...
[INFO] [stdout] 426 |                    maybe_field!(&attach.bl, false)?;
[INFO] [stdout]     |                    ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this method call relies on the `impl<T> Into<T> for T` blanket implementation and type inference, which is a semver hazard as a new `impl Into<_>` that affects your type might be added in the future causing type inference errors
[INFO] [stdout]     = note: you can instead use the fully-qualified path `<TypstError<'_> as Into<TypstError<'_>>::into(val) to avoid triggering this lint
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: useless conversion to the same type: `TypstError<'_>`
[INFO] [stdout]    --> src/types/content/sequence/chumsky/parser.rs:401:40
[INFO] [stdout]     |
[INFO] [stdout] 392 | /                  macro_rules! field {
[INFO] [stdout] 393 | |                      ($field:expr, $canonical:expr) => {{
[INFO] [stdout] 394 | |                          variable::<LocatingSequence<'this, 'data>, E>($canonical)
[INFO] [stdout] 395 | |                              .parse(<LocatingSequence as From<&'this Content<'data>>>::from(
[INFO] [stdout] ...   |
[INFO] [stdout] 401 | |                                  return TypstError::full(
[INFO] [stdout]     | | ________________________________________^
[INFO] [stdout] 402 | ||                                     span,
[INFO] [stdout] 403 | ||                                     "Invalid Variable Subscript/Superscript",
[INFO] [stdout] 404 | ||                                     "Variable like declaration in attachment",
[INFO] [stdout] ...   ||
[INFO] [stdout] 411 | ||                                 .into();
[INFO] [stdout]     | ||_______________________________________^
[INFO] [stdout] 412 | |                              })
[INFO] [stdout] 413 | |                      }};
[INFO] [stdout] 414 | |                  }
[INFO] [stdout]     | |__________________- this error originates in the macro `field` which comes from the expansion of the macro `maybe_field`
[INFO] [stdout] ...
[INFO] [stdout] 427 |                    maybe_field!(&attach.br, false)?;
[INFO] [stdout]     |                    ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this method call relies on the `impl<T> Into<T> for T` blanket implementation and type inference, which is a semver hazard as a new `impl Into<_>` that affects your type might be added in the future causing type inference errors
[INFO] [stdout]     = note: you can instead use the fully-qualified path `<TypstError<'_> as Into<TypstError<'_>>::into(val) to avoid triggering this lint
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: useless conversion to the same type: `TypstError<'_>`
[INFO] [stdout]    --> src/types/content/sequence/chumsky/parser.rs:401:40
[INFO] [stdout]     |
[INFO] [stdout] 392 | /                  macro_rules! field {
[INFO] [stdout] 393 | |                      ($field:expr, $canonical:expr) => {{
[INFO] [stdout] 394 | |                          variable::<LocatingSequence<'this, 'data>, E>($canonical)
[INFO] [stdout] 395 | |                              .parse(<LocatingSequence as From<&'this Content<'data>>>::from(
[INFO] [stdout] ...   |
[INFO] [stdout] 401 | |                                  return TypstError::full(
[INFO] [stdout]     | | ________________________________________^
[INFO] [stdout] 402 | ||                                     span,
[INFO] [stdout] 403 | ||                                     "Invalid Variable Subscript/Superscript",
[INFO] [stdout] 404 | ||                                     "Variable like declaration in attachment",
[INFO] [stdout] ...   ||
[INFO] [stdout] 411 | ||                                 .into();
[INFO] [stdout]     | ||_______________________________________^
[INFO] [stdout] 412 | |                              })
[INFO] [stdout] 413 | |                      }};
[INFO] [stdout] 414 | |                  }
[INFO] [stdout]     | |__________________- this error originates in the macro `field` which comes from the expansion of the macro `maybe_field`
[INFO] [stdout] ...
[INFO] [stdout] 430 |                        maybe_field!(&attach.t, false)?;
[INFO] [stdout]     |                        ------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this method call relies on the `impl<T> Into<T> for T` blanket implementation and type inference, which is a semver hazard as a new `impl Into<_>` that affects your type might be added in the future causing type inference errors
[INFO] [stdout]     = note: you can instead use the fully-qualified path `<TypstError<'_> as Into<TypstError<'_>>::into(val) to avoid triggering this lint
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: useless conversion to the same type: `TypstError<'_>`
[INFO] [stdout]    --> src/types/content/sequence/chumsky/parser.rs:401:40
[INFO] [stdout]     |
[INFO] [stdout] 392 | /                  macro_rules! field {
[INFO] [stdout] 393 | |                      ($field:expr, $canonical:expr) => {{
[INFO] [stdout] 394 | |                          variable::<LocatingSequence<'this, 'data>, E>($canonical)
[INFO] [stdout] 395 | |                              .parse(<LocatingSequence as From<&'this Content<'data>>>::from(
[INFO] [stdout] ...   |
[INFO] [stdout] 401 | |                                  return TypstError::full(
[INFO] [stdout]     | | ________________________________________^
[INFO] [stdout] 402 | ||                                     span,
[INFO] [stdout] 403 | ||                                     "Invalid Variable Subscript/Superscript",
[INFO] [stdout] 404 | ||                                     "Variable like declaration in attachment",
[INFO] [stdout] ...   ||
[INFO] [stdout] 411 | ||                                 .into();
[INFO] [stdout]     | ||_______________________________________^
[INFO] [stdout] 412 | |                              })
[INFO] [stdout] 413 | |                      }};
[INFO] [stdout] 414 | |                  }
[INFO] [stdout]     | |__________________- this error originates in the macro `field` which comes from the expansion of the macro `maybe_field`
[INFO] [stdout] ...
[INFO] [stdout] 432 |                    maybe_field!(&attach.tl, false)?;
[INFO] [stdout]     |                    ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this method call relies on the `impl<T> Into<T> for T` blanket implementation and type inference, which is a semver hazard as a new `impl Into<_>` that affects your type might be added in the future causing type inference errors
[INFO] [stdout]     = note: you can instead use the fully-qualified path `<TypstError<'_> as Into<TypstError<'_>>::into(val) to avoid triggering this lint
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: useless conversion to the same type: `TypstError<'_>`
[INFO] [stdout]    --> src/types/content/sequence/chumsky/parser.rs:401:40
[INFO] [stdout]     |
[INFO] [stdout] 392 | /                  macro_rules! field {
[INFO] [stdout] 393 | |                      ($field:expr, $canonical:expr) => {{
[INFO] [stdout] 394 | |                          variable::<LocatingSequence<'this, 'data>, E>($canonical)
[INFO] [stdout] 395 | |                              .parse(<LocatingSequence as From<&'this Content<'data>>>::from(
[INFO] [stdout] ...   |
[INFO] [stdout] 401 | |                                  return TypstError::full(
[INFO] [stdout]     | | ________________________________________^
[INFO] [stdout] 402 | ||                                     span,
[INFO] [stdout] 403 | ||                                     "Invalid Variable Subscript/Superscript",
[INFO] [stdout] 404 | ||                                     "Variable like declaration in attachment",
[INFO] [stdout] ...   ||
[INFO] [stdout] 411 | ||                                 .into();
[INFO] [stdout]     | ||_______________________________________^
[INFO] [stdout] 412 | |                              })
[INFO] [stdout] 413 | |                      }};
[INFO] [stdout] 414 | |                  }
[INFO] [stdout]     | |__________________- this error originates in the macro `field` which comes from the expansion of the macro `maybe_field`
[INFO] [stdout] ...
[INFO] [stdout] 433 |                    maybe_field!(&attach.tr, false)?;
[INFO] [stdout]     |                    ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this method call relies on the `impl<T> Into<T> for T` blanket implementation and type inference, which is a semver hazard as a new `impl Into<_>` that affects your type might be added in the future causing type inference errors
[INFO] [stdout]     = note: you can instead use the fully-qualified path `<TypstError<'_> as Into<TypstError<'_>>::into(val) to avoid triggering this lint
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `sertyp` (lib test) due to 8 previous errors
[INFO] [stderr] warning: build failed, waiting for other jobs to finish...
[INFO] [stdout] error: useless conversion to the same type: `S`
[INFO] [stdout]   --> src/types/content/sequence/error.rs:51:41
[INFO] [stdout]    |
[INFO] [stdout] 51 |         move |span: S| TypstError::full(span.into(), label.into(), expected.into(), found.into())
[INFO] [stdout]    |                                         ^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: this method call relies on the `impl<T> Into<T> for T` blanket implementation and type inference, which is a semver hazard as a new `impl Into<_>` that affects your type might be added in the future causing type inference errors
[INFO] [stdout]    = note: `#[deny(self_type_conversion)]` on by default
[INFO] [stdout] help: consider removing the conversion call
[INFO] [stdout]    |
[INFO] [stdout] 51 -         move |span: S| TypstError::full(span.into(), label.into(), expected.into(), found.into())
[INFO] [stdout] 51 +         move |span: S| TypstError::full(span, label.into(), expected.into(), found.into())
[INFO] [stdout]    |
[INFO] [stdout] help: you can use the fully-qualified path to avoid triggering this lint
[INFO] [stdout]    |
[INFO] [stdout] 51 -         move |span: S| TypstError::full(span.into(), label.into(), expected.into(), found.into())
[INFO] [stdout] 51 +         move |span: S| TypstError::full(<S as Into<_>>::into(span), label.into(), expected.into(), found.into())
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: useless conversion to the same type: `TypstError<'_>`
[INFO] [stdout]    --> src/types/content/sequence/chumsky/parser.rs:401:40
[INFO] [stdout]     |
[INFO] [stdout] 392 |                   macro_rules! field {
[INFO] [stdout] ...
[INFO] [stdout] 401 |                                   return TypstError::full(
[INFO] [stdout]     |  ________________________________________^
[INFO] [stdout] 402 | |                                     span,
[INFO] [stdout] 403 | |                                     "Invalid Variable Subscript/Superscript",
[INFO] [stdout] 404 | |                                     "Variable like declaration in attachment",
[INFO] [stdout] ...   |
[INFO] [stdout] 411 | |                                 .into();
[INFO] [stdout]     | |_______________________________________^
[INFO] [stdout] ...
[INFO] [stdout] 424 |                   field!(&**attach.base, true)?;
[INFO] [stdout]     |                   ---------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this method call relies on the `impl<T> Into<T> for T` blanket implementation and type inference, which is a semver hazard as a new `impl Into<_>` that affects your type might be added in the future causing type inference errors
[INFO] [stdout]     = note: you can instead use the fully-qualified path `<TypstError<'_> as Into<TypstError<'_>>::into(val) to avoid triggering this lint
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: useless conversion to the same type: `TypstError<'_>`
[INFO] [stdout]    --> src/types/content/sequence/chumsky/parser.rs:401:40
[INFO] [stdout]     |
[INFO] [stdout] 392 | /                  macro_rules! field {
[INFO] [stdout] 393 | |                      ($field:expr, $canonical:expr) => {{
[INFO] [stdout] 394 | |                          variable::<LocatingSequence<'this, 'data>, E>($canonical)
[INFO] [stdout] 395 | |                              .parse(<LocatingSequence as From<&'this Content<'data>>>::from(
[INFO] [stdout] ...   |
[INFO] [stdout] 401 | |                                  return TypstError::full(
[INFO] [stdout]     | | ________________________________________^
[INFO] [stdout] 402 | ||                                     span,
[INFO] [stdout] 403 | ||                                     "Invalid Variable Subscript/Superscript",
[INFO] [stdout] 404 | ||                                     "Variable like declaration in attachment",
[INFO] [stdout] ...   ||
[INFO] [stdout] 411 | ||                                 .into();
[INFO] [stdout]     | ||_______________________________________^
[INFO] [stdout] 412 | |                              })
[INFO] [stdout] 413 | |                      }};
[INFO] [stdout] 414 | |                  }
[INFO] [stdout]     | |__________________- this error originates in the macro `field` which comes from the expansion of the macro `maybe_field`
[INFO] [stdout] ...
[INFO] [stdout] 425 |                    maybe_field!(&attach.b, false)?;
[INFO] [stdout]     |                    ------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this method call relies on the `impl<T> Into<T> for T` blanket implementation and type inference, which is a semver hazard as a new `impl Into<_>` that affects your type might be added in the future causing type inference errors
[INFO] [stdout]     = note: you can instead use the fully-qualified path `<TypstError<'_> as Into<TypstError<'_>>::into(val) to avoid triggering this lint
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: useless conversion to the same type: `TypstError<'_>`
[INFO] [stdout]    --> src/types/content/sequence/chumsky/parser.rs:401:40
[INFO] [stdout]     |
[INFO] [stdout] 392 | /                  macro_rules! field {
[INFO] [stdout] 393 | |                      ($field:expr, $canonical:expr) => {{
[INFO] [stdout] 394 | |                          variable::<LocatingSequence<'this, 'data>, E>($canonical)
[INFO] [stdout] 395 | |                              .parse(<LocatingSequence as From<&'this Content<'data>>>::from(
[INFO] [stdout] ...   |
[INFO] [stdout] 401 | |                                  return TypstError::full(
[INFO] [stdout]     | | ________________________________________^
[INFO] [stdout] 402 | ||                                     span,
[INFO] [stdout] 403 | ||                                     "Invalid Variable Subscript/Superscript",
[INFO] [stdout] 404 | ||                                     "Variable like declaration in attachment",
[INFO] [stdout] ...   ||
[INFO] [stdout] 411 | ||                                 .into();
[INFO] [stdout]     | ||_______________________________________^
[INFO] [stdout] 412 | |                              })
[INFO] [stdout] 413 | |                      }};
[INFO] [stdout] 414 | |                  }
[INFO] [stdout]     | |__________________- this error originates in the macro `field` which comes from the expansion of the macro `maybe_field`
[INFO] [stdout] ...
[INFO] [stdout] 426 |                    maybe_field!(&attach.bl, false)?;
[INFO] [stdout]     |                    ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this method call relies on the `impl<T> Into<T> for T` blanket implementation and type inference, which is a semver hazard as a new `impl Into<_>` that affects your type might be added in the future causing type inference errors
[INFO] [stdout]     = note: you can instead use the fully-qualified path `<TypstError<'_> as Into<TypstError<'_>>::into(val) to avoid triggering this lint
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: useless conversion to the same type: `TypstError<'_>`
[INFO] [stdout]    --> src/types/content/sequence/chumsky/parser.rs:401:40
[INFO] [stdout]     |
[INFO] [stdout] 392 | /                  macro_rules! field {
[INFO] [stdout] 393 | |                      ($field:expr, $canonical:expr) => {{
[INFO] [stdout] 394 | |                          variable::<LocatingSequence<'this, 'data>, E>($canonical)
[INFO] [stdout] 395 | |                              .parse(<LocatingSequence as From<&'this Content<'data>>>::from(
[INFO] [stdout] ...   |
[INFO] [stdout] 401 | |                                  return TypstError::full(
[INFO] [stdout]     | | ________________________________________^
[INFO] [stdout] 402 | ||                                     span,
[INFO] [stdout] 403 | ||                                     "Invalid Variable Subscript/Superscript",
[INFO] [stdout] 404 | ||                                     "Variable like declaration in attachment",
[INFO] [stdout] ...   ||
[INFO] [stdout] 411 | ||                                 .into();
[INFO] [stdout]     | ||_______________________________________^
[INFO] [stdout] 412 | |                              })
[INFO] [stdout] 413 | |                      }};
[INFO] [stdout] 414 | |                  }
[INFO] [stdout]     | |__________________- this error originates in the macro `field` which comes from the expansion of the macro `maybe_field`
[INFO] [stdout] ...
[INFO] [stdout] 427 |                    maybe_field!(&attach.br, false)?;
[INFO] [stdout]     |                    ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this method call relies on the `impl<T> Into<T> for T` blanket implementation and type inference, which is a semver hazard as a new `impl Into<_>` that affects your type might be added in the future causing type inference errors
[INFO] [stdout]     = note: you can instead use the fully-qualified path `<TypstError<'_> as Into<TypstError<'_>>::into(val) to avoid triggering this lint
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: useless conversion to the same type: `TypstError<'_>`
[INFO] [stdout]    --> src/types/content/sequence/chumsky/parser.rs:401:40
[INFO] [stdout]     |
[INFO] [stdout] 392 | /                  macro_rules! field {
[INFO] [stdout] 393 | |                      ($field:expr, $canonical:expr) => {{
[INFO] [stdout] 394 | |                          variable::<LocatingSequence<'this, 'data>, E>($canonical)
[INFO] [stdout] 395 | |                              .parse(<LocatingSequence as From<&'this Content<'data>>>::from(
[INFO] [stdout] ...   |
[INFO] [stdout] 401 | |                                  return TypstError::full(
[INFO] [stdout]     | | ________________________________________^
[INFO] [stdout] 402 | ||                                     span,
[INFO] [stdout] 403 | ||                                     "Invalid Variable Subscript/Superscript",
[INFO] [stdout] 404 | ||                                     "Variable like declaration in attachment",
[INFO] [stdout] ...   ||
[INFO] [stdout] 411 | ||                                 .into();
[INFO] [stdout]     | ||_______________________________________^
[INFO] [stdout] 412 | |                              })
[INFO] [stdout] 413 | |                      }};
[INFO] [stdout] 414 | |                  }
[INFO] [stdout]     | |__________________- this error originates in the macro `field` which comes from the expansion of the macro `maybe_field`
[INFO] [stdout] ...
[INFO] [stdout] 430 |                        maybe_field!(&attach.t, false)?;
[INFO] [stdout]     |                        ------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this method call relies on the `impl<T> Into<T> for T` blanket implementation and type inference, which is a semver hazard as a new `impl Into<_>` that affects your type might be added in the future causing type inference errors
[INFO] [stdout]     = note: you can instead use the fully-qualified path `<TypstError<'_> as Into<TypstError<'_>>::into(val) to avoid triggering this lint
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: useless conversion to the same type: `TypstError<'_>`
[INFO] [stdout]    --> src/types/content/sequence/chumsky/parser.rs:401:40
[INFO] [stdout]     |
[INFO] [stdout] 392 | /                  macro_rules! field {
[INFO] [stdout] 393 | |                      ($field:expr, $canonical:expr) => {{
[INFO] [stdout] 394 | |                          variable::<LocatingSequence<'this, 'data>, E>($canonical)
[INFO] [stdout] 395 | |                              .parse(<LocatingSequence as From<&'this Content<'data>>>::from(
[INFO] [stdout] ...   |
[INFO] [stdout] 401 | |                                  return TypstError::full(
[INFO] [stdout]     | | ________________________________________^
[INFO] [stdout] 402 | ||                                     span,
[INFO] [stdout] 403 | ||                                     "Invalid Variable Subscript/Superscript",
[INFO] [stdout] 404 | ||                                     "Variable like declaration in attachment",
[INFO] [stdout] ...   ||
[INFO] [stdout] 411 | ||                                 .into();
[INFO] [stdout]     | ||_______________________________________^
[INFO] [stdout] 412 | |                              })
[INFO] [stdout] 413 | |                      }};
[INFO] [stdout] 414 | |                  }
[INFO] [stdout]     | |__________________- this error originates in the macro `field` which comes from the expansion of the macro `maybe_field`
[INFO] [stdout] ...
[INFO] [stdout] 432 |                    maybe_field!(&attach.tl, false)?;
[INFO] [stdout]     |                    ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this method call relies on the `impl<T> Into<T> for T` blanket implementation and type inference, which is a semver hazard as a new `impl Into<_>` that affects your type might be added in the future causing type inference errors
[INFO] [stdout]     = note: you can instead use the fully-qualified path `<TypstError<'_> as Into<TypstError<'_>>::into(val) to avoid triggering this lint
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: useless conversion to the same type: `TypstError<'_>`
[INFO] [stdout]    --> src/types/content/sequence/chumsky/parser.rs:401:40
[INFO] [stdout]     |
[INFO] [stdout] 392 | /                  macro_rules! field {
[INFO] [stdout] 393 | |                      ($field:expr, $canonical:expr) => {{
[INFO] [stdout] 394 | |                          variable::<LocatingSequence<'this, 'data>, E>($canonical)
[INFO] [stdout] 395 | |                              .parse(<LocatingSequence as From<&'this Content<'data>>>::from(
[INFO] [stdout] ...   |
[INFO] [stdout] 401 | |                                  return TypstError::full(
[INFO] [stdout]     | | ________________________________________^
[INFO] [stdout] 402 | ||                                     span,
[INFO] [stdout] 403 | ||                                     "Invalid Variable Subscript/Superscript",
[INFO] [stdout] 404 | ||                                     "Variable like declaration in attachment",
[INFO] [stdout] ...   ||
[INFO] [stdout] 411 | ||                                 .into();
[INFO] [stdout]     | ||_______________________________________^
[INFO] [stdout] 412 | |                              })
[INFO] [stdout] 413 | |                      }};
[INFO] [stdout] 414 | |                  }
[INFO] [stdout]     | |__________________- this error originates in the macro `field` which comes from the expansion of the macro `maybe_field`
[INFO] [stdout] ...
[INFO] [stdout] 433 |                    maybe_field!(&attach.tr, false)?;
[INFO] [stdout]     |                    ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this method call relies on the `impl<T> Into<T> for T` blanket implementation and type inference, which is a semver hazard as a new `impl Into<_>` that affects your type might be added in the future causing type inference errors
[INFO] [stdout]     = note: you can instead use the fully-qualified path `<TypstError<'_> as Into<TypstError<'_>>::into(val) to avoid triggering this lint
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `sertyp` (lib) due to 8 previous errors
[INFO] running `Command { std: "docker" "inspect" "2e46f8b572e6cde59b0d172db8289ac9003a59bbf61f76ab4faf9117ca26ad77", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "2e46f8b572e6cde59b0d172db8289ac9003a59bbf61f76ab4faf9117ca26ad77", kill_on_drop: false }`
[INFO] [stdout] 2e46f8b572e6cde59b0d172db8289ac9003a59bbf61f76ab4faf9117ca26ad77
