I don't like the use of "safe" and "fast" similar to why I don't like
"crypto". They're too vague and (in the case of "safe") there is no
guarantee that they have that property.

If one is overwhelmingly concerned with these properties, they will
probably bring in portable library code they or someone else has
benchmarked for whatever statistical / performance properties are
needed. It's less likely that an implementation specified library will
do that, it's a burden.

-- Peter McGoron