Parallel alternative parsers

Open
#3,075 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
haskell
Domain
backend

Research direction

Start by reading the alternative combinator implementation and the parser code it composes. Compare the proposed sequential and concurrent strategies, including whether to use the second parser only after the first fails or whichever yields first. Done means implementing and validating a chosen strategy, but the issue does not specify which strategy or where to test it.

Written by the indexing model from the issue text.

Description

aspect:parsers

In an alternative combinator we can feed the input in parallel to both the parsers until one of the parsers yields a result. We could use different strategies for using the result e.g. (1) compute in parallel but use the second parser only if the first parser fails, (2) use whichever parser yields the result first and discard the other.

The parallel parsing could be done sequentially or concurrently.

Dominant language
Haskell
Stars
926
Forks
71
Avg merge
6h 49m
Merged PRs (30d)
3

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from composewell/streamly

All issues in composewell/streamly

Similar issues

More Haskell issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.