[libc++] Document the de-facto status of compiler extension support (#110877)

This was brought up in a maintainer's meeting a few months ago. This
simply documents the current status quo.
This commit is contained in:
Louis Dionne 2024-10-07 17:27:29 -04:00 committed by GitHub
parent 9e06e772a1
commit 5c88aa9d34
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -317,6 +317,15 @@ Unpoisoning may not be an option, if (for example) you are not maintaining the a
* You are using allocator, which does not call destructor during deallocation.
* You are aware that memory allocated with an allocator may be accessed, even when unused by container.
Support for compiler extensions
-------------------------------
Clang, GCC and other compilers all provide their own set of language extensions. These extensions
have often been developed without particular consideration for their interaction with the library,
and as such, libc++ does not go out of its way to support them. The library may support specific
compiler extensions which would then be documented explicitly, but the basic expectation should be
that no special support is provided for arbitrary compiler extensions.
Platform specific behavior
==========================