1. It does not define the behavior when the bounds is exceeded. When using the '-Warray-bounds' option (with gcc) the compiler does its best to detect at compile time boundary violations, but it does not add bounds check at runtime since it has no behavior to apply to this event. The remaining bounds violations are therefore ignored.
2. It does not cover the allocation of such arrays (or fat-pointer). Given the description it could look like a VLA or something like that for heap allocated arrays:
size_t size = 3;
int (*arr)[size] = malloc(sizeof(*arr));
I doubt that many developers will do so.In the end, my personal opinion is in favor of this kind of feature in modern languages. But C is a specific language that addresses the need for a language that has fine control over memory and this kind of feature is not mandatory for this type of language (But maybe it's worth it? As long as it completely addresses the issue).
This problem makes me wonder:
Isn't the real mistake to use C (which is a language that allows a fine control over memory) for large applications containing a lot of logic (like a kernel)? The C language (or equivalent) will always be useful for low-level software interfaces with hardware that use memory in an unconventional way. But languages that contain a lot of logic have other constraints that are not necessarily compatible.
We can also combine these two types of languages into one, Rust for example distinguishes between these two worlds with the keyword unsafe.