[clang frontend] RFC: Enforcing Bounds Safety in C https://discourse.llvm.org/t/rfc-enforcing-bounds-safety-in-c-fbounds-safety/70854
This profile might be incomplete.
Open on tech.lgbt FélixPersonal infoAbout:
he/him 🏳️🌈 compiler intruder 🦅 memory safety hawk 🍎
Wall 1 post
[clang frontend] RFC: Enforcing Bounds Safety in C https://discourse.llvm.org/t/rfc-enforcing-bounds-safety-in-c-fbounds-safety/70854 |
@fay59 Bikeshedding: I dislike that `__single` implicitly allows null where most of the others do not. Did you consider a non-null `__single` alongside a new `__single_or_null` ?
How do these interact with the existing nullability attributes such as `nonnull` and `_Nonnull` and `_Nullable` ? (examples: Does __single+nonnull optimize away null checks? Does __counted_by+_Nullable convert to __counted_by_or_null? generate a compiler error?)
@fay59 it's missing a mention of this, which is already found in the whole Windows SDK https://learn.microsoft.com/en-us/cpp/code-quality/understanding-sal?view=msvc-170
* Are bounds dynamic expressions like VLAs? Can I __counted_by(2* size)?
* Can I split an allocation?
* Performance?