Closed MarkReedZ closed 3 months ago
Yes, familiar with that. Do you know of a good way to avoid that warning?
simsimd_f16_t is _Float16 so I presume this PR is okay, but haven't tested it on sapphire yet. Was there a reason we had to use _Float16 or was it just an oversight?
I wanted to make it independent from the alias, and used _Float16
similar to Intel docs.
We have the following warnings. I can replace _Float16 with simsimd_f16_t