I disagree with this reasoning. It’s a serious problem in theory, but not in practice. So it’s a problem that can be delayed while the other puzzle pieces find their homes. There is much work to be done, and navigating the best path through this work is part of the fun of the project. Sometimes that means focusing on the language, and sometimes that means focusing on the tooling such as the build system.
In reality, nearly all of the suggestions of everyone to modify the Zig language, including myself, are fatally flawed. In order to make language changes happen that ultimately solve real world use cases satisfactorily while fitting snugly into the rest of the design of the language, it requires me to have several long meetings with only 1-2 other people whose skills include identifying quickly why an idea won’t work. Ideas are cheap. Everybody has them and according to my observation, everyone kinda has the same ideas as each other. What makes good ideas happen is when the critical feedback quickly rejects idea after idea after idea, finally making me and those others in the meeting reach for something different, something creative; something that actually solves the problems.
Regarding aliasing specifically, I still have some audacious ideas to try.