There must be a library that provides the opportunity for the best performance, before sugary libs get all layered over the top, and it's asI've said twice now, everyone will have a different idea of what that sugarAPI will look like, so I feel it should live above this... or perhapsbeside this (in the same file?), but I wouldn't want to remove this API infavour of a vector 'class'.
Having those generalized intrinsics publicly available in same file probably makes sense.
