Parallel alternative parsers
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
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
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
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from composewell/streamly
-
takeInterval yields nothing, dropInterval drops nothingPossibly taken @GuillaumedeVolpiano claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
composewell/streamly#3271 ·
-
Parser: many accepts input that ends inside an elementPossibly taken @GuillaumedeVolpiano claimed this 1 day ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 52/100
composewell/streamly#3270 ·
-
aspect:api
Difficulty 4/5 1-2 days Newbie friendliness 48/100
composewell/streamly#3206 ·
-
api:breaking aspect:api aspect:filesystem
Difficulty 4/5 1-2 days Newbie friendliness 35/100
composewell/streamly#3203 ·
-
type:performance
Difficulty 4/5 3-5 days Newbie friendliness 32/100
composewell/streamly#3200 · 2 comments ·
All issues in composewell/streamly
Similar issues
-
bug desktop
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
simplex-chat/simplex-chat#8291 ·
Maintainers usually reply within 1 day
-
[BUG]: C# programs with top-level statements fail to compilePossibly taken @AsyncNigam claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
compiler-explorer/compiler-explorer#9625 · 1 comment ·
Maintainers usually reply within 1 day
-
needs triage type: enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 3 days
-
reflex-0.10Open
Difficulty 1/5 Under an hour Newbie friendliness 62/100
commercialhaskell/stackage#8180 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
OpenZeppelin/canton-contracts#140 ·
Maintainers usually reply within 1 day