Skip to content

Use Padding and make private public padding fields - #5444

Open
dybucc wants to merge 1 commit into
rust-lang:mainfrom
dybucc:add-padding-remaining-public
Open

Use Padding and make private public padding fields#5444
dybucc wants to merge 1 commit into
rust-lang:mainfrom
dybucc:add-padding-remaining-public

Conversation

@dybucc

@dybucc dybucc commented Aug 28, 2026

Copy link
Copy Markdown
Contributor

Description

Stems from #5435, but contains only the parts of the
patchset that affect currently public record fields.

Checklist

  • Relevant tests in libc-test/semver have been updated
  • Commit messages permalink to headers for added or changed API
  • Placeholder or unstable values like *LAST or *MAX have the
    standard doc comment
  • Tested locally (cargo test -p libc-test --target mytarget);
    especially relevant for platforms that may not be checked in CI

@rustbot

rustbot commented Aug 28, 2026

Copy link
Copy Markdown
Collaborator

Some changes occurred in an OpenBSD module

cc @semarie

Some changes occurred in a solarish module

cc @jclulow, @pfmooney

Some changes occurred in a NetBSD-like module

cc @semarie

Some changes occurred in an Android module

cc @maurer

Change public padding fields to be both private and use the `Padding`
type. This has already been the norm for some time now, but there was
still some cruft left. This patch finishes up the work, though this
comes at the cost of breaking changes.
@dybucc
dybucc force-pushed the add-padding-remaining-public branch from 988168b to e75fae0 Compare August 30, 2026 13:47
@rustbot

rustbot commented Aug 30, 2026

Copy link
Copy Markdown
Collaborator

This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed.

Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.

@tgross35 tgross35 changed the title crate: use Padding and make private public padding fields Use Padding and make private public padding fields Aug 31, 2026
@rustbot

rustbot commented Aug 31, 2026

Copy link
Copy Markdown
Collaborator

☔ The latest upstream changes (possibly #5434) made this pull request unmergeable. Please resolve the merge conflicts.

@tgross35 tgross35 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tgross35 tgross35 added the stable-declined This change is breaking, difficult to backport, low priority, or otherwise not relevant for 0.2 label Aug 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants