Well, you could choose to slow runtime and use `X.data.astype`.

Or unilaterally declare that pairwise distances are only available for standard float types and adjust the comments accordingly.

I think you should do the former (or extend the fused type and take a compile-time hit) since user-friendliness will require checking and raising an explicit error for that case anyway.