EmbarkStudios / rust-gpu

When trying to get this project working with more recent versions of dependencies I get the following with spirv-std bumped to 0.7.0

error[E0599]: no method named `token` found for struct `LitStr` in the current scope
   --> C:\....\.cargo\registry\src\index.crates.io-6f17d22bba15001f\spirv-std-macros-0.7.0\src\lib.rs:790:65
    |
790 | ...                   new_t.push(TokenTree::Literal(l.token()));
    |                                                       ^^^^^ method not found in `LitStr`

I bumped the rust-toolchain.toml to the same as in this repo fwiw.

Does this go away when you run cargo update -p syn? If so, the issue is that we only require an old version:

rust-gpu/crates/spirv-std/macros/Cargo.toml

Line 17 in a64857a

syn = { version = "1.0.58", features = ["full", "visit-mut"] }

But some other dependencies are forcing newer versions:

rust-gpu/Cargo.lock

Lines 2386 to 2388 in a64857a

    
           [[package]] 
        
           name = "syn" 
        
           version = "1.0.105"

Thankfully, this shouldn't affect newer projects, as Cargo will always pick the newest version when creating the Cargo.lock, but it is a mistake on our part and we should be careful with dependencies like that.

This is probably not strong enough, but we should at least run cargo update -Z minimal-versions in CI, to force dependency versions in Cargo.toml files to be large enough to allow building & passing tests (cc @repi).

But I just tried that and it fails to compile anyhow 1.0.0, so that probably means the ecosystem isn't necessarily readily to do something that broad. Also, it would perhaps be nicer if we just forced version bumps in Cargo.lock to be reflected in Cargo.toml, instead, but I can't find a command that would make the two equal.

EDIT: turns out that this can be used by making an isolated package that depends on spirv-std alone.
(as the deps broken by -Z minimal-versions are all on the host side)

@dsvensson I've opened a tentative fix:

#1054

But note that the simplest fix for that project is still likely running cargo update -p syn.

Aha, doh, so deleting Cargo.lock and rebuilding, should have tried. 🤦‍♂️ Thanks, works now.

Aha, doh, so deleting Cargo.lock and rebuilding, should have tried.

No, that's a really bad idea, you want to minimize Cargo.lock changes, not maximize them.
The command I gave you should only update the syn version, not unrelated crates.

When you're trying to fix something, you shouldn't change unrelated things that could cause other complications.

Agree generally, but this is a small toy project almost no deps, and I'm just scouting around various vulkan related projects.

Unable to compile `spirv-std-macros` with old `Cargo.lock`.