Error when proc macro derive output doesn't fully parse#87316
Conversation
|
(rust-highfive has picked a reviewer for you, use r? to override) |
|
@bors try |
|
⌛ Trying commit 2bd0a21321c4908e865e641fee5e532f03c37788 with merge 279ba2cff36a3029611d32ee1b5c82559c565f69... |
|
☀️ Try build successful - checks-actions |
|
@craterbot check |
|
👌 Experiment ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
80bf842 to
6024115
Compare
|
🚧 Experiment ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
|
🎉 Experiment
|
|
Not a lot of regressions. Haven't looked at all of them yet, but most of them seem to be about an extra
We sould probably not error and produce a future-incompatible warning for an extra |
|
Analyzed the results now. By far the most cases are from Two are in crates that have a very low number of downloads and haven't been updated in a long time. The last few seem to be through In all cases it's a semicolon at the end of the token stream, without anything following it. So no items got silently ignored. |
|
With the number of regressions this large (>10) we've been typically adding deprecation lints in the past, the lint can be immediately made deny-by-default in this case, I think. |
|
@m-ou-se What is the status of this PR? |
|
I need to change this from a hard error to a lint. But I've not had time for that yet. |
|
☔ The latest upstream changes (presumably #94584) made this pull request unmergeable. Please resolve the merge conflicts. |
See #87314
Fixes #87314