with-utf8 VS unicode-transforms

Compare with-utf8 vs unicode-transforms and see what are their differences.


Get your IO right on the first try (by serokell)


Fast Unicode normalization in Haskell (by composewell)
Our great sponsors
  • SonarQube - Static code analysis for 29 languages.
  • Scout APM - Less time debugging, more time building
  • OPS - Build and Run Open Source Unikernels
with-utf8 unicode-transforms
2 1
39 40
- -
5.9 6.8
28 days ago 20 days ago
Haskell Haskell
Mozilla Public License 2.0 BSD 3-clause "New" or "Revised" License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.


Posts with mentions or reviews of with-utf8. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-02-15.


Posts with mentions or reviews of unicode-transforms. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-04-17.
  • [ANN] unicode-collation 0.1
    3 projects | reddit.com/r/haskell | 17 Apr 2021
    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?

When comparing with-utf8 and unicode-transforms you can also consider the following projects:

haskell-language-server - Official haskell ide support via language server (LSP). Successor of ghcide & haskell-ide-engine.

hashable - A class for types that can be converted to a hash value

refined - Refinement types with static checking

lens - Lenses, Folds, and Traversals - Join us on freenode #haskell-lens

hnix - A Haskell re-implementation of the Nix expression language

primitive - This package provides various primitive memory-related operations.

jump - Jump start your Haskell development

unordered-containers - Efficient hashing-based container types

critbit - A Haskell implementation of crit-bit trees.

resource-pool - A high-performance striped resource pooling implementation for Haskell

text-icu - This package provides the Haskell Data.Text.ICU library, for performing complex manipulation of Unicode text.

Frames - Data frames for tabular data.