msvc::no_unique_address
- Dominant language
- C++
- Stars
- 80
- Forks
- 184
- Avg merge
- 1h 16m
- Merged PRs (30d)
- 3
Description
According to https://devblogs.microsoft.com/cppblog/msvc-cpp20-and-the-std-cpp20-switch/#c20-no_unique_address , MSVC ignores `[[no_unique_address]]`, but some versions provide `[[msvc::no_unique_address]]` and actually act on it (this has also been added to compatible compilers like clang-18+).
Would it make sense for BOOST_ATTRIBUTE_NO_UNIQUE_ADDRESS to expand to this attribute under the right conditions?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the definition and usage of BOOST_ATTRIBUTE_NO_UNIQUE_ADDRESS, then read the linked MSVC C++20 guidance to identify the affected compiler versions and conditions. The work is done when the macro selects msvc::no_unique_address where supported without regressing other compiler paths, with the relevant Boost.Config checks passing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100