Usearch

What's Changed
* Test: Use `const` instead of `var` in JS by abetomo in https://github.com/unum-cloud/usearch/pull/479
* Make: Rust Windows builds by brkp in https://github.com/unum-cloud/usearch/pull/472
* Docs: Update JavaScript code example by abetomo in https://github.com/unum-cloud/usearch/pull/478
* Mixed Precision Kernels, Windows Builds, and Docs by ashvardanian in https://github.com/unum-cloud/usearch/pull/476

New Contributors
* brkp made their first contribution in https://github.com/unum-cloud/usearch/pull/472

**Full Changelog**: https://github.com/unum-cloud/usearch/compare/v2.15.0...v2.15.1

- [x] Get API for ObjC and Swift 455
- [x] Feature parity between C and GoLang 409
- [x] Swift & Obj-C bindings for `filteredSearch` 471

Thanks to abetomo, sdenton4, brittlewis12, vardhan, and MarkReedZ for help 🤗

Previously, on modern CPUs the USearch index would default to `f16` IEEE 16-bit floating point numbers, when used through high-level bindings, like Python. That format is more common in the Pythonic ecosystem, and it's supported by NumPy. Still, it's much less efficient and harder to convert to/from `f32`. The alternative is to use `bf16`, which is more hardware friendly, and upcast to `f32`, when we need to export the data back to Python. That's the new default behavior.

What's Changed

* Default to `bf16` by ashvardanian in https://github.com/unum-cloud/usearch/pull/465

**Full Changelog**: https://github.com/unum-cloud/usearch/compare/v2.13.5...v2.14.0

Last few releases of USearch for Rust didn't include SimSIMD. Expect things to get much faster, if you are a 🦀 user 🤗