I'm facing this error during compile for linux: type annotations needed for Box<_>

[shahverd]

Check for existing issues

• Completed

Describe the bug / provide steps to reproduce it

    Compiling time v0.3.28
error[E0282]: type annotations needed for `Box<_>`
  --> /home/mostafa/.cargo/registry/src/index.crates.io-6f17d22bba15001f/time-0.3.28/src/format_description/parse/mod.rs:83:9
   |
83 |     let items = format_items
   |         ^^^^^
...
86 |     Ok(items.into())
   |              ---- type must be known at this point
   |
help: consider giving `items` an explicit type, where the placeholders `_` are specified
   |
83 |     let items: Box<_> = format_items
   |              ++++++++

For more information about this error, try `rustc --explain E0282`.
error: could not compile `time` (lib) due to 1 previous error

Environment

I don't know the alternative for copy system specs into clipboard on linux.

If applicable, add mockups / screenshots to help explain present your vision of the feature

No response

If applicable, attach your ~/Library/Logs/Zed/Zed.log file to this issue.

No response

[SomeoneToIgnore]

What's your rustc version, does it match

zed/rust-toolchain.toml

Line 2 in d5fe2c8

channel = "1.78"

?

[SomeoneToIgnore]

Also note that you cannot compile a dependency crate, not Zed per se, so not really related to Zed.

[shahverd]

my rustc version is as above. Also I have tried 1.80

[SomeoneToIgnore]

Our Linux CI shows that building is possible on a daily basis, people seem to have no compliation issues related to Rust, and also my local tests on a clean VM show the same:

So, closing this optimistically as something broken with the local set-up.

I see 2 possibilities:

• zed project directory has some rustc overrides or otherwise the toolchain version is not the same.
  I would try running cargo --version to ensure things are working.

• The crate source code could've been edited or anyhow else damaged.
  I would remove /home/mostafa/.cargo/registry/src/index.crates.io-6f17d22bba15001f/time-0.3.28/ and try to recompile.

Maybe, there's something else is off, but I cannot deduce that from such sparse details.

[fala13]

Had the exact same compilation issue on different project - deleting Cargo.lock solved it.

[jonmayer]

I am seeing the exact same failure with time-0.3.28 -- I'm running on stable (rustc/cargo version 1.80.0, but on ARM architecture (stable-aarch64-unknown-linux-gnu). (I don't see why deleting Cargo.lock would make a difference but I'll try it and report back.)

[jonmayer]

Ah, I see the error is being tracked in the time-rs project: time-rs/time#696

Looks like they have a fix (as of 18 hours ago).

[BassManFH]

Same here, cargo update resolved the issue, although time-rs wasn't updated.

[AliBigdeli0]

Same here, cargo update resolved the issue, although time-rs wasn't updated.

I just used cargo update and it solved my problem.

[kevin-valerio]

For other folks coming here in the future, I had this issue by doing cargo install mydependency --locked, removing the --locked made it worked :)