Keep the signature of concatIterate and parConcatIterate the same

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
haskell
Domain
backend

Research direction

Start by comparing the signatures of concatIterate and parConcatIterate and reading their implementations; the issue does not name files or tests. Determine what changes are needed to make the signatures match, then check existing tests for both functions and run the relevant suite. Done means concatIterate uses the intended signature without breaking its behavior.

Written by the indexing model from the issue text.

Description

parConcatIterate has a cleaner signature. We can try implementing concatIterate using that signature.

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.