There a million ways your code can break downstream dependencies, generic code is just one of them. Breaking stuff when you change things is just in the nature

There a million ways your code can break downstream dependencies, generic code is just one of them. Breaking stuff when you change things is just in the nature of it, which is why not changing APIs is so important. But I'd rather have the compiler errors you describe as something my IDE can jump to, than to spend hours poking around in opaque macro black boxes, because half of every library is a huge chunk of copy pasted code and macro magic to get around the type system. Rust as is, is a de Bruijn criteria fulfilling proof language, with the macro system ending up as the meta language.