>> The library provides the literal suffixes _y and _d. Is there a reason why
>> there's no _m?
> Yes. I gave it some thought and decided against it. 3_m looks too much like "3
> meters". Especially if this library gets standardized, then 3_m becomes 3m.
> And that would forbid the C++ std::lib from ever developing a units library
> with meters in it.
I get forward thinking & future planning, but c++ has no business standardizing distance/volume/area/etc type units now or going forward. it might be nice to have the conversion constants to multiply, but its way, way out of scope at the language level. Time is important in general purpose programming; its a special case.
that said, I do suppose meters per min is valid, if strange.