Skip to content

v0.8.0

Compare
Choose a tag to compare
@theodore-s-beers theodore-s-beers released this 23 Feb 16:10

In this minor release:

  • I've tried to limit allocation by having the collator object hold onto two collation element arrays—one for each string being compared in a given call of the collate method—which can be repeatedly overwritten. Previously, a new vector was initialized every time that a collation element array was generated. This change might have produced a small performance benefit? I don't think it's a bad idea, anyway. I have been surprised by how "stuck" the library seems to be at its current level of performance. Did the compiler already find all these optimizations?
  • The API has changed a bit: the collator object once again needs to be declared as mutable. This is because of the aforementioned collation element arrays.
  • Other miscellaneous dependency updates, refactoring, and general housekeeping