Skip to content

Commit

Permalink
Add README (#10)
Browse files Browse the repository at this point in the history
  • Loading branch information
meooow25 authored Mar 2, 2024
1 parent 3f9cb64 commit 275a5a1
Showing 1 changed file with 94 additions and 0 deletions.
94 changes: 94 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
@@ -1 +1,95 @@
# parser-regex

[![Haskell-CI](https://github.com/meooow25/parser-regex/actions/workflows/haskell-ci.yml/badge.svg)](https://github.com/meooow25/parser-regex/actions/workflows/haskell-ci.yml)

Regex based parsers

## Features

* Parsers based on [regular expressions](https://en.wikipedia.org/wiki/Regular_expression),
capable of parsing [regular languages](https://en.wikipedia.org/wiki/Regular_language).
There are no extra features that would make parsing non-regular languages
possible.
* Regexes are composed using combinators.
* Resumable parsing of sequences of any type containing values of any type.
* Special support for `Text` and `String` in the form of convenient combinators
and operations like find and replace.
* Parsing runtime is linear in the length of the sequence being parsed. No
exponential backtracking.

## Usage

```hs
{-# LANGUAGE OverloadedStrings #-}
import Control.Applicative (optional)
import Data.Text (Text)
import qualified Data.Text as T

import qualified Regex.Text as R
import qualified Data.CharSet as CS

data URI = URI
{ scheme :: Maybe Text
, authority :: Maybe Text
, path :: Text
, query :: Maybe Text
, fragment :: Maybe Text
} deriving Show

-- ^(([^:/?#]+):)?(//([^/?#]*))?([^?#]*)(\?([^#]*))?(#(.*))?
-- A non-validating regex to extract parts of a URI, from RFC 3986
-- Translated:
uriRE :: R.REText URI
uriRE = URI
<$> optional (R.someTextOf (CS.not ":/?#") <* R.char ':')
<*> optional (R.text "//" *> R.manyTextOf (CS.not "/?#"))
<*> R.manyTextOf (CS.not "?#")
<*> optional (R.char '?' *> R.manyTextOf (CS.not "#"))
<*> optional (R.char '#' *> R.manyText)

-- >>> R.reParse uriRE "https://github.com/meooow25/parser-regex?tab=readme-ov-file#parser-regex"
-- Just (URI { scheme = Just "https"
-- , authority = Just "github.com"
-- , path = "/meooow25/parser-regex"
-- , query = Just "tab=readme-ov-file"
-- , fragment = Just "parser-regex" })
```

## Alternatives

### `regex-applicative`

[`regex-applicative`](https://hackage.haskell.org/package/regex-applicative) is
the primary inspiration for this library, and provides a similar set of
features.
`parser-regex` attempts to be a more fully-featured library built on the
ideas of `regex-applicative`.

### Traditional regex libraries

Other alternatives are more traditional regex libraries that use regex patterns,
like [`regex-tdfa`](https://hackage.haskell.org/package/regex-tdfa) and
[`regex-pcre`](https://hackage.haskell.org/package/regex-pcre)/
[`regex-pcre-builtin`](https://hackage.haskell.org/package/regex-pcre-builtin).

Reasons to use `parser-regex` over traditional regex libraries:

* You prefer parser combinators over regex patterns
* You need more powerful parsing capabilities than just submatch extraction
* You need to parse a sequence type that is not supported by these regex
libraries

Reasons to use traditional regex libraries over `parser-regex`:

* The terseness of regex patterns is better suited for your use case
* You need something very fast, and adversarial input is not a concern.
Use `regex-pcre`/`regex-pcre-builtin`.

For a more detailed comparison of regex libraries, see
[here](https://github.com/meooow25/parser-regex/tree/master/bench).

## Contributing

Questions, bug reports, documentation improvements, code contributions welcome!
Please [open an issue](https://github.com/meooow25/parser-regex/issues) as the
first step.

0 comments on commit 275a5a1

Please sign in to comment.