Skip to content

type-layout: mention that call ABI compatibility is a separate concern #1608

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.

Sign up for GitHub

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 1 commit into from
Sep 17, 2024
Merged

type-layout: mention that call ABI compatibility is a separate concern #1608

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions src/type-layout.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,10 @@ of type layout.
Type layout can be changed with each compilation. Instead of trying to document
exactly what is done, we only document what is guaranteed today.

Note that even types with the same layout can still differ in how they are passed
across function boundaries. For function call ABI compatibility of types,
see [here][fn-abi-compatibility].

## Size and Alignment

All values have an alignment and size.
Expand Down Expand Up @@ -593,6 +597,7 @@ used with any other representation.
[`Copy`]: std::marker::Copy
[dynamically sized types]: dynamically-sized-types.md
[field-less enums]: items/enumerations.md#field-less-enum
[fn-abi-compatibility]: ../core/primitive.fn.md#abi-compatibility
[enumerations]: items/enumerations.md
[zero-variant enums]: items/enumerations.md#zero-variant-enums
[undefined behavior]: behavior-considered-undefined.md
Expand Down