I can understand some general reasons for the push-back on allowing aliasing.

But specifically double and std::float64_t on platforms, where they have the same representation:

What is gained by disallowing aliasing? Wouldn't it just be defined as a typedef on those platforms?

You find yourself agreeing (with disallowing), can you explain?

-----Ursprüngliche Nachricht-----
Von: Paul Caprioli <paul@hpkfft.com>

There is push-back on allowing aliasing (i.e., on prohibiting TBAA optimizations based on double and std::float64_t being different types).
Unfortunately, I find myself agreeing.