Skip to content

C.183: Mention bit_cast as a C++20+ solution #2293

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
wants to merge 1 commit into
base: master
Choose a base branch
from
+3 −1
Open

C.183: Mention bit_cast as a C++20+ solution #2293

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
4 changes: 3 additions & 1 deletion CppCoreGuidelines.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9032,7 +9032,9 @@ but at least we can see that something tricky is going on.)
Unfortunately, `union`s are commonly used for type punning.
We don't consider "sometimes, it works as expected" a conclusive argument.

C++17 introduced a distinct type `std::byte` to facilitate operations on raw object representation. Use that type instead of `unsigned char` or `char` for these operations.
Modern C++ introduced `std::byte` (C++17) and `std::bit_cast` (C++20) to facilitate operations on raw object representations.
Use `reinterpret_cast` along with `std::byte` instead of `unsigned char` or `char` for these operations.
For `std::bit_cast`, if there is no value of the return type (the `To` type) corresponding to the value representation produced, the behavior is undefined.

##### Enforcement

Expand Down