This isn't entirely true. Rust's indexing operator performs a dynamic check but the language and stdlib have a number of ways to access array elements without indexing, which is effectively a form of static checking. For example, the following loop is statically guaranteed to not go OOB, and will not emit any unnecessary bounds checks:

  for i in some_arr {
    println!("{i}");
  }

I suspect most techniques you could think of to statically avoid bounds checks are possible in rust's type system.

▲ uecker an hour ago | parent [-]

These are not terribly interesting cases though, as it would also be impossible to get an oob access in other languages either.

▲ wasmperson 35 minutes ago | parent [-]

Yes, rust didn't invent the concept of an iterator, and is thus not the only language which offers a solution to statically avoid bounds checks. Feel free to give a more "interesting" case you believe rust wouldn't be able to handle.

	▲	uecker 10 minutes ago \| parent [-]
		Rust fails to prove basic indirection to be statically safe and instead does a run-time check. `fn main() { let v = vec![1, 2, 3]; v[5]; }`