text
Haskell library for space- and time-efficient operations over Unicode text. (by haskell)
attoparsec
A fast Haskell library for parsing ByteStrings (by haskell)
Our great sponsors
| text | attoparsec | |
|---|---|---|
| 13 | 6 | |
| 396 | 509 | |
| 0.8% | 0.6% | |
| 8.4 | 3.7 | |
| 3 days ago | 4 days ago | |
| C++ | Haskell | |
| BSD 2-clause "Simplified" License | 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.
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.
text
Posts with mentions or reviews of text.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-05-25.
- Super Colliding Nix Stores: Nix Flakes for Millions of Developers
-
The Spinnaker Programming Language
String is a linked list of UTF-32 codepoints, which is just as bad as it sounds. Haskell programmers usually use Text from the text package instead.
-
[ANN] GHCup-0.1.19.0 released
This is the first release that was executed via the new GitHub CI. Everything went smoothly, except for an unexpected packaging bug on windows due to text-2.0 linking against libstdc++ by default.
-
Limits of possible performance improvements of Haskell/GHC code?
In addition to what's mentioned, the "default" libraries people use are often not the best-performing ones. E.g. Data.Vector.Hashtables is often much faster than Data.HashMap.Strict (which again is typically faster than Data.Map). And we find performance papercuts in common libraries that may simply be due to not enough people optimising for speed.
-
What is the idiomatic way to test "hidden" module functions in a Cabal project
Used by nearly every Haskell project: https://hackage.haskell.org/package/text 60% of the modules are ".Internal".
- Monthly Hask Anything (June 2022)
-
Haskell - Important Libraries
text
-
Switch internal representation to UTF8 by Bodigrim · Pull Request #365 · haskell/text
Here is a representative patch for text: https://github.com/haskell/text/pull/365/commits/37a2157245457a287d638bbceb472fe93b71f224 Hopefully it clarifies why achieving C performance is problematic even if you have enough primitive operations.
- Size hints for streams in text package
-
Can I wait forever without getLine?
I want to run an app in a Docker container, but detached. This causes getLine to throw an EOF exception, since the terminal detaches. That is, if I understand this thread correctly https://github.com/haskell/text/issues/258.
attoparsec
Posts with mentions or reviews of attoparsec.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-03-24.
-
Functional Implementation of a parser?
The basic idea is to create a state monad (usually using the State monad transformer) which contains a string to be parsed, and which also lifts other monad transformers like Except for throwing syntax errors. Or you can use a parser combinator like Parser provided by a parsing library like Megaparsec or Attoparsec that defines an efficient State+Except monad transformer combination for you.
-
Haskell - Important Libraries
attoparsec
-
On a daily base in this sub
good libraries for parsing: parsec, attoparsec etc.
- Parser Combinators in Haskell
-
Splitting html tags string into list of string
The more "idiomatic" way would be to use a parser library, e.g. parsec, attoparsec, or megaparsec. But even then I think it would be a lot easier to maintain if you could preserve the angle brackets <> in the input.
-
Ditch regex for parser combinators, a Rust / nom step-by-step guide
- https://hackage.haskell.org/package/attoparsec - https://hackage.haskell.org/package/megaparsec
What are some alternatives?
When comparing text and attoparsec you can also consider the following projects:
attempt - Concrete data type for handling extensible exceptions as failures.
megaparsec - Industrial-strength monadic parser combinator library
base58string - Bitcoin script compilation, manipulation and decompilation
parsec - A monadic parser combinator library
algebraic-classes - Conversions between algebraic classes and F-algebras.
attoparsec-parsec - An Attoparsec compatibility layer for Parsec
text-ansi
attoparsec-data - Parsers for the standard Haskell data types
text-trie - An efficient finite map from Text to values, based on bytestring-trie.
parsers - Generic parser combinators
gps2htmlReport - Generates a HTML page report detailing a GPS journey, with charts, statistics and an OpenStreetMap graphic.
parser-combinators - Lightweight package providing commonly useful parser combinators