-
Notifications
You must be signed in to change notification settings - Fork 214
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
Core-foundation-sys shouldn't have changed version at all #96
Comments
It's too late now anyway, but it's a heads up for the next time. |
Hopefully the 24 people who watch this repo will be aware of this and will reject a PR that bumps |
I am not sure why you employ such a tone to convey your annoyance, and this is not a "semver issue". While it seems this could have been 0.2.4, doing a breaking bump doesn't break semver. I assume you are fed up because of rust-windowing/glutin#853, but this wouldn't have happened if glutin had said |
@nox It has nothing to do with that but with the |
No, core-foundation 0.3 was selected by Cargo in glutin only because Cargo does weird stuff with a single digit |
I'm not talking about glutin's breakage here. It's totally glutin's fault and my fault for accepting a PR in the past that did I'm opening this because we can't bump to core-foundation 0.3 without causing breakages in the entire ecosystem. |
Add support for CGEvent value fields <!-- Reviewable:start --> This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/core-graphics-rs/96) <!-- Reviewable:end -->
Because its Cargo.toml contains a
links
attribute, it is impossible to usecore-foundation-sys v0.2
andcore-foundation-sys v0.3
in the same project.There is absolutely no reason why the version of
core-foundation-sys
should match the version ofcore-foundation
.The text was updated successfully, but these errors were encountered: