-
Notifications
You must be signed in to change notification settings - Fork 13.4k
rustdoc JSON: Don't apply #[repr]
privacy heuristics
#141126
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this!
If we felt like making this part of the cargo-semver-checks experience super nice, including the layout info of fields would be lovely:
repr(C)
type had field X change offset / alignment / size." These would be part of our ABI lint group, which isn't quite SemVer but people e.g. working on embedded systems have found useful nonetheless.repr(transparent)
public API" logic, which we can otherwise only approximate as "some field ispub
so we'll assume it's the non-1-ZST one." That heuristic is generally fine in practice AFAICT, but doing better is always good :)None of this is an emergency of course. Just wanted to give you info on what else in this general area would be useful info to have.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you put this in an issue (or on zulip)? I think it’ll be forgotten here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll leave a reminder for myself when I get back home. I'll likely be ~offline until Thursday or so due to travel, so that's the earliest I'd be able to open one — it's 11pm here at the moment and I'm going to bed now.
If someone else were to open an issue for this in the meantime, I wouldn't be upset at all. No pressure of course, just proactively opting in.