Tracking issue for pref_align_of intrinsic #91971
Labels
A-intrinsics
Area: intrinsics
C-tracking-issue
Category: A tracking issue for an RFC or an unstable feature.
S-tracking-design-concerns
Status: There are blocking ❌ design concerns.
S-tracking-needs-summary
Status: It's hard to tell what's been done and what hasn't! Someone should do some investigation.
T-lang
Relevant to the language team, which will review and decide on the PR/issue.
T-libs-api
Relevant to the library API team, which will review and decide on the PR/issue.
Comments
RalfJung
added
the
C-tracking-issue
Mark-Simulacrum
added
T-lang
joshtriplett
added
S-tracking-design-concerns
|
Context for labels applied: it sounds like we need a summary of what precisely this means, as distinct from |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This intrinsic returns the "preferred" alignment of a type, which can be different from the minimal alignment exposed via
mem::align_of. It is not currently exposed through any wrapper method, but can still be accessed by unstable code using theintrinsicsorcore_intrinsicsfeatures.See #90877 for why it cannot be removed; the short summary is some code is actually using it. So let's have a place to centralize discussion about the intrinsics. (This is not a regular tracking issue because there is no associated feature gate, but close enough I think.)
The text was updated successfully, but these errors were encountered: