After some thought, I think I know why this is irritating. The domains I imagine Zig would be suited for are also ones where I use vector operations regularly. Almost a 1:1 overlap:
- Embedded (Accelerations, velocities, positions)
- Robotics
- Games
- Performance-critical scientific and numerical code (Cosmology, computational chemistry etc)
- 3D graphics and visualizations
Zig has builtin support for vectors[1], which I think provides some alleviation. But sure, it's not as complete or flexible as a whole vector/matrix library.
Great to know! From the description in that page and yours, it sounds like this is a related, but different concept. Specifically, that page includes use of a `Vec3` of the sort I was implementing, done with a `struct` and methods, vice @Vector.
