-
-
Notifications
You must be signed in to change notification settings - Fork 78
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
Type aliases of types defined outside the current crate are not checked #473
Comments
Actually, semver-checks will detect
but not the moved type mentioned above. |
If you use cf25b7d943624947ff027b38f75ce0a451b01eb0 instead it now shows no changes detected. |
Thanks for the report. This is a known issue, caused in part by the same limitation that also causes #355: use std::os::raw::{c_uint, c_void, c_int, c_short, c_uchar, c_ushort};
// ...
pub type UniChar = c_ushort; and The limitation is due to the fact that external types' definitions are not part of the rustdoc JSON file of the scanned crate. There is currently no good way to connect data in multiple rustdoc JSON files together. The rustdoc team is aware of this limitation and is interested in resolving it; I've stayed in touch with them on this. Sorry I don't have a better answer! |
Is there an issue tracking the rustdoc problem? |
This is the closest thing to a single tracking issue I could find: rust-lang/compiler-team#635 That's a prerequisite |
We ended up getting burnt with this with the release of core-foundation-sys 0.8.5. servo/core-foundation-rs#619 a |
Steps to reproduce the bug with the above code
Run
cargo semver-checks check-release
in thecore-foundation-sys
directory of https://github.com/servo/core-foundation-rs @ eb00adae0c6d3694dccc54b195132c2929ac8c96Actual Behaviour
No changes detected
Expected Behaviour
semver-checks fails to detect that
UniChar
has moved fromstring::
tobase::
Generated System Information
Software version
cargo-semver-checks 0.21.0
Operating system
Mac OS X 10.15.6 (Darwin 19.6.0)
Command-line
cargo version
Compile time information
Build Configuration
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: