Well, that didn't go as planned. Right after v1.0.0, another API change was required to fix a soundness bug.
So instead of going for v2.0.0 right away, I yanked v1.0.0 to replace it with this one.
Changes
- Previously, striding and padding logic leaked into the user API via
KMeansStatestruct. Padded/strided buffers now use theStrideBufferstruct that still allows accessing the raw memory inside kmeans, but only allows unpadded access outside of kmeans - Critical Fix: Replace broken custom aligned buffer allocation with
aligned-veccrate