Let's hold off until Adam has a look at georust/rstar#181 – #1254 is open to enable #1246, but #1246 depends on a new API in rstar 0.12.1 so would be blocked by this anyway.

I'm ok to wait for a little bit, but my primary concern isn't the new feature in #1246, but rather on geo users getting incorrect results in the meanwhile.

It looks like resolution is imminent with georust/rstar#184

Anyone opposed to my following up with patch releases to geo-types and geo to require rstar = "0.12.2" ?

Do we need to do that if we yank rstar 0.12.1?

0.12.1 is yanked

I'm not sure!

What happens if you run cargo update -p geo in your project? Is it possible to update geo while keeping the yanked version of rstar around?

Answering my own question: cargo update -p geo will not proactively update it's rstar dependency, even if the current version has been yanked.

Unless we make a new release, the user would need to either run (unqualified) cargo update or know to run cargo update -p rstar.

Proof:

$ cargo update -p geo
    Updating crates.io index
     Locking 0 packages to latest compatible versions
note: pass `--verbose` to see 5 unchanged dependencies behind latest

$ cargo tree | rg rstar
    │   └── rstar v0.12.0
    ├── rstar v0.12.0 (*)

$ cargo update -p rstar
    Updating crates.io index
     Locking 1 package to latest compatible version
    Updating rstar v0.12.0 -> v0.12.2
note: pass `--verbose` to see 4 unchanged dependencies behind latest

$ cargo tree | rg rstar
  Downloaded rstar v0.12.2
  Downloaded 1 crate (43.8 KB) in 0.19s
    │   └── rstar v0.12.2
    ├── rstar v0.12.2 (*)

Annoying. Thanks for figuring that out!

Where did we land on this after yesterday's discussion? My understanding is that there was a 24 hour (ish) period during which, if you updated your geo dependency, or started a new project and included it, you'd end up with a perf-regressed and buggy geo, which WOULD be fixed with a full cargo update but WOULDN'T be fixed with a cargo update -p geo.

I think Cargo givea a warning if you have a yanked crate in your lockfile. Should be relatively easy to test.