What are Rust's hidden implementation details that most devs never see?
I've been working with Rust for couple years now and really love how clean the abstraction layers are compared to other languages I use
The thing that got me thinking about this - every language has those moments where you dig deeper and suddenly realize "oh wait, this thing I thought worked one way actually works completely different under the hood"
Like in Python when you discover that `len()` isn't just a regular method call but uses magic methods because of all the mutability stuff happening behind scenes. Or how C lets you do weird things like `5[array]` instead of `array[5]` because it's all just pointer arithmetic anyway
Rust seems really good at keeping these implementation details hidden from daily programming, but I'm curious what kinds of things are happening under surface that most people never run into
What are some examples where Rust's abstractions start showing their seams if you look close enough? The kind of stuff that works fine 99% of time but then you hit some edge case and suddenly need to understand what's really going on