- unicode-transforms VS with-utf8
- unicode-transforms VS refined
- unicode-transforms VS hashable
- unicode-transforms VS jump
- unicode-transforms VS hnix
- unicode-transforms VS critbit
- unicode-transforms VS code-builder
- unicode-transforms VS resource-pool
- unicode-transforms VS lens
- unicode-transforms VS primitive
Unicode-transforms Alternatives
Similar projects and alternatives to unicode-transforms
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
text-icu
This package provides the Haskell Data.Text.ICU library, for performing complex manipulation of Unicode text.
NOTE:
The number of mentions on this list indicates mentions on common posts plus user suggested alternatives.
Hence, a higher number means a better unicode-transforms alternative or higher similarity.
unicode-transforms reviews and mentions
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
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.
Stats
Basic unicode-transforms repo stats
1
47
2.5
6 months ago
composewell/unicode-transforms is an open source project licensed under BSD 3-clause "New" or "Revised" License which is an OSI approved license.
The primary programming language of unicode-transforms is Haskell.
Popular Comparisons
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com