unicode-collation
unicode-transforms
unicode-collation | unicode-transforms | |
---|---|---|
3 | 1 | |
16 | 47 | |
- | - | |
6.3 | 2.5 | |
4 months ago | 6 months ago | |
Haskell | Haskell | |
GNU General Public License v3.0 or later | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
unicode-collation
-
Looking for projects that make heavy use of IntMap which have benchmarks
https://github.com/jgm/unicode-collation uses IntMap quite a bit and has benchmarks.
-
[ANN] unicode-collation 0.1
Why don't you open an issue at https://github.com/jgm/unicode-collation -- it would be a better place to hash out the details than here.
-
Text Maintainers: text-utf8 migration discussion - Haskell Foundation
There are several native Haskell libraries, covering individual features of text-icu: https://hackage.haskell.org/package/unicode-transforms for normalization https://github.com/jgm/unicode-collation for collation https://github.com/composewell/unicode-data for character database https://hackage.haskell.org/package/unicode-general-category for character database
unicode-transforms
-
[ANN] unicode-collation 0.1
Thanks! Here's a puzzle. Profiling shows that about a third of the time in my code is spent in normalize from unicode-transforms. (Normalization is a required step in the algorithm but can be omitted if you know that the input is already in NFD form.) And when I add a benchmark that omits normalization, I see run time cut by a third. But text-icu's run time in my benchmark doesn't seem to be affected much by whether I set the normalization option. I am not sure how to square that with the benchmarks here that seem to show unicode-transforms outperforming text-icu in normalization. text-icu's documentation says that "an incremental check is performed to see whether the input data is in FCD form. If the data is not in FCD form, incremental NFD normalization is performed." I'm not sure exactly what this means, but it may mean that text-icu avoids normalizing the whole string, but just normalizes enough to do the comparison, and sometimes avoids normalization altogether if it can quickly determine that the string is already normalized. I don't see a way to do this currently with unicode-transforms.
What are some alternatives?
haskell-code-explorer - Web application for exploring and understanding Haskell codebases
with-utf8 - Get your IO right on the first try
text-icu - This package provides the Haskell Data.Text.ICU library, for performing complex manipulation of Unicode text.
refined - Refinement types with static checking
hashable - A class for types that can be converted to a hash value
jump - Jump start your Haskell development
code-builder - Packages for defining APIs, running them, generating client code and documentation.
critbit - A Haskell implementation of crit-bit trees.
hnix - A Haskell re-implementation of the Nix expression language
resource-pool - A high-performance striped resource pooling implementation for Haskell
lens - Lenses, Folds, and Traversals - Join us on web.libera.chat #haskell-lens
primitive - This package provides various primitive memory-related operations.