-
-
Notifications
You must be signed in to change notification settings - Fork 265
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Breaking change from 2.1.3 to 2.2.1 due to new RuleType bound on Error types #693
Comments
@dennis-hamester thanks for the report. @pest-parser/maintainers @pest-parser/triage any thoughts on how to resolve it? Revert that commit and release a new version? Or keep it as it is and be more careful next time (E.g. with https://crates.io/crates/cargo-semver-checks)? Or release it as v3.0.0 (despite it not being the "mythical pest3" with the new grammar etc.)? |
I think leaving it as is and adding a check is probably reasonable, perhaps with a note on the release? |
I could go either way. I agree it's not a huge deal. Maybe a comment on the offending type would help? Note that, ultimately, we'll probably need to go to v3.0.0 before "mythical pest3", so the sooner we get that over and done with, the better? |
This is simple enough to fix, though. Just remove the trait bound from the type. Not bounding on the |
The patch looks all right, so I guess we'll yank |
👍 sounds accurate to me |
Actually, the release may be |
FYI I haven't checked all crates, but
|
Describe the bug
In commit 5b807be,
Error<R>
was changed toError<R: RuleType>
, which is a breaking change. As far as I can see, this also extends toErrorVariant
.To Reproduce
Compiles with Pest 2.1.3, but not with 2.2.1:
To make it compile with 2.2.1, a bound on
R
must be added:Additional context
For me personally, this is not a huge deal. My code didn't require any bigger changes to make it compile again. But it can certainly be surprising.
The text was updated successfully, but these errors were encountered: