You'll only get fireballs inside the atmosphere. In space, you'll get jets.

Could easily be solved by not pointing a gun at anything you don't want to lose. How difficult can that be?

It kind of makes sense in C, as arrays are basically pointers. e.g. p[i] == *(p + i)

One advantage to null-terminated strings is that there's typical only one format - well one for each character type at least. For length encoded strings, the format depends on the register size, and the endianness of the platform. Of course C does not enforce the use of zero-terminated strings. Not even for string literals.

for (int i = 0; i < 10; ++i) { something(); }

I remember when some compilers would treat this like:

int i; for (i = 0; i < 10; ++i) { something(); }

and others like this:

{ for (int i = 0; i < 10; ++i) something(); }

As the standard, for whatever reason, decide to change it. So much for not breaking existing code.

There's a lot of evidence we won't. We would have found it by now if someone has discovered it in the future.

I think garbage collection is a library issue, not something that should be in the core language by default.

I'd like to see runtime reflection with the proviso that it's static. It's my thinking that reflection should be compile-time for a compiled language.