Skip to content

Remove the tinyvec resolution constraint once 1.13.x builds #340

Description

@leynos

tinyvec 1.13.0 does not build on the nightly this repository pins. Its
src/tinyvec.rs imports alloc::vec as a module and then invokes the vec!
macro, so the macro no longer resolves:

error: cannot find macro `vec` in this scope
   --> tinyvec-1.13.0/src/tinyvec.rs:710:21
    |
710 |       TinyVec::Heap(vec![A::Item::default(); len])
    |                     ^^^
note: `vec` is imported here, but it is a module, not a macro
   --> tinyvec-1.13.0/src/tinyvec.rs:3:18
    |
  3 | use alloc::vec::{self, Vec};

tinyvec reaches this workspace transitively through Bevy's text and font
stack. This repository commits no Cargo.lock, so every build resolves the
newest compatible release and reaches the broken one. make lint and any
--all-features build fail on untouched main, reproduced on a clean
detached checkout with an isolated target directory.

The constraint tinyvec = "~1.12" in Cargo.toml holds resolution at 1.12
until this is fixed upstream. It is a resolution constraint only; no code in
this workspace names the crate.

Upstream: 1.13.0 was published 2026-09-03 at 21:13 UTC and is not yanked.
Lokathor/tinyvec#225 reports the same failure and Lokathor/tinyvec#226
proposes the fix.

Removal condition

Remove the tinyvec entry from Cargo.toml once a fixed release is published
and resolvable, or once 1.13.0 is yanked. Verify with make lint on a clean
checkout before removing.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workinglowBacklog work, hygiene, or technical debt planned opportunistically, without a strict deadline.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions