@bors2 try

⌛ Trying commit e4ad46e with merge 8d46be7...

To cancel the try build, run the command @bors2 try cancel.

☀️ Try build successful (CI)
Build commit: 8d46be7 (8d46be77cd48fdbcced888d027457e2c9cf2aa16, parent: 2fcf1776b9ccef89993dfe40e9f5c4908e2d2d48)

@craterbot check

👌 Experiment pr-142723 created and queued.
🤖 Automatically detected try build 8d46be7
🔍 You can check out the queue and this experiment's details.

i️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more

🚧 Experiment pr-142723 is now running

i️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more

🎉 Experiment pr-142723 is completed!
📊 3143 regressed and 10 fixed (650587 total)
📰 Open the full report.

⚠️ If you notice any spurious failure please add them to the denylist!
i️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more

Various versions of epaint, glyph_brush, and taffy seem to account for the vast majority of the breakage. Whatever else we do, it'd probably be worth putting in PRs for those.

@traviscross I don't think we should submit any PRs to those crates until we have agreement that we're prepared to break passing e.g. 2.0 to a method taking Into<f32>. Because I think the likely response to such a PR is "wait, what?".

We've speculatively submitted PRs before in these kind of cases. Such PRs said, essentially, that the code being changed was relying on something that had become an open question. But I'm happy with whatever the people pushing this forward want to do (or not do) in this regard.

taffy is actually already fixed from when the impl was breifly added on nightly a year ago (DioxusLabs/taffy#643): all the regressions caused by that crate are from other crates using outdated 0.3.* and 0.4.* versions of it (the fix is in 0.3.19 and 0.4.3 and later).

(I plan to do a full write-up of the Crater run soon, I just haven't had time yet.)