Skip to content

[diff.basic] Fix errors in entry about C "compatible" types #8664

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

Open
hubert-reinterpretcast wants to merge 2 commits into
base: main
Choose a base branch
from
Open

[diff.basic] Fix errors in entry about C "compatible" types #8664

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8a1586c
[diff.basic] Use enum example instead of example outdated since C99
hubert-reinterpretcast Dec 17, 2025
b2b6ad6
[diff.basic] Stop claiming, as harmless, type-based aliasing violations
hubert-reinterpretcast Dec 17, 2025
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
12 changes: 5 additions & 7 deletions source/compatibility.tex
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2916,21 +2916,19 @@

\diffref{basic.types}
\change
C allows ``compatible types'' in several places, \Cpp{} does not.\\
C allows mixing between ``compatible types'' in several places where \Cpp{} does not.\\
For example,
otherwise-identical \keyword{struct} types with different tag names
are ``compatible'' in C but are distinctly different types
in \Cpp{}.
enumerated types are ``compatible'' with their underlying types in C but, in \Cpp{},
enumerations are types distinct from their underlying types.
\rationale
Stricter type checking is essential for \Cpp{}.
\effect
Deletion of semantically well-defined feature.
\difficulty
Semantic transformation.
The ``typesafe linkage'' mechanism will find many, but not all,
of such problems.
Those problems not found by typesafe linkage will continue to
function properly,
such problems.
Some cases are allowed by \Cpp{}
according to the ``layout compatibility rules'' of this
document.
\howwide
Expand Down