YexuanXiao wrote: > So we're making `__SIZE_TYPE__` be some magic type that you cannot name, only > procure out of thin air through using sizeof? That doesn't seem like a good > idea to me.
Within standard scope, it generally does not pose any risks unless X-macros are used. I have actually suggested a similar change to MSVC, although they do not provide size_t through __SIZE_TYPE__. https://github.com/llvm/llvm-project/pull/155979 _______________________________________________ cfe-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
