You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
msvc and known_semantics are not reserved identifiers in the C++ Standard, so users are allowed to #define them to anything, which may break every header that directly uses [[msvc::known_semantics]] (e.g. <type_traits>).
IIUC the Standard equivalently requires that every non-Standard attribute used in a Standard header to be spelled in reserved identifiers, e.g. [[__msvc__::__known_semantics__]]. Does MSVC support such spelling?
The text was updated successfully, but these errors were encountered:
Define `_MSVC_MEOW` macro in `<yvals_core.h>`for each `[[msvc::meow]]` custom attribute with surrounding push_macro/pop_macro guards.
Fixesmicrosoft#2645
Per Discord discussion, we should probably give up battling the preprocessor and just have the compiler front end implement ugly equivalents of the pertinent attributes.
msvc
andknown_semantics
are not reserved identifiers in the C++ Standard, so users are allowed to#define
them to anything, which may break every header that directly uses[[msvc::known_semantics]]
(e.g.<type_traits>
).IIUC the Standard equivalently requires that every non-Standard attribute used in a Standard header to be spelled in reserved identifiers, e.g.
[[__msvc__::__known_semantics__]]
. Does MSVC support such spelling?The text was updated successfully, but these errors were encountered: