unicode-transforms
text-icu
Our great sponsors
unicode-transforms | text-icu | |
---|---|---|
1 | 2 | |
47 | 46 | |
- | - | |
2.5 | 6.1 | |
6 months ago | 17 days ago | |
Haskell | Haskell | |
BSD 3-clause "New" or "Revised" License | 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-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.
text-icu
-
[ANN] unicode-collation 0.1
Until now, the only way to do proper Unicode sorting in Haskell was to depend on text-icu, which wraps the C library icu4c. However, there are disadvantages to depending on an external C library. In addition, the last release of text-icu was in 2015, and since then there have been changes to icu4c that cause build-failures, as noted in this issue.
-
Haskell ghost knowledge; difficult to access, not written down
text-icu occasionally breaks horribly and nondeterministically (1, 2) despite being praised by SOTU
What are some alternatives?
with-utf8 - Get your IO right on the first try
text-stream-decode - Streaming decoding functions for UTF encodings.
refined - Refinement types with static checking
gps2htmlReport - Generates a HTML page report detailing a GPS journey, with charts, statistics and an OpenStreetMap graphic.
hashable - A class for types that can be converted to a hash value
text-trie - An efficient finite map from Text to values, based on bytestring-trie.
jump - Jump start your Haskell development
observable-sharing - Observable sharing for haskell
code-builder - Packages for defining APIs, running them, generating client code and documentation.
hebrew-time - Hebrew dates and prayer times.
critbit - A Haskell implementation of crit-bit trees.
text-binary - Binary instances for strict and lazy Text data types