Adithya Kumar

This needs to be reviewed very carefully.

Nested termination in folds and parsers

1

`Fold.many` and `Parse.many` are functions with no termination. The default termination reapplies the parsing/folding combinator. `Parse.many` itself can have a natural nesting termination by terminating on parser failure Folds on...

We already have most test cases in `Streamly.Test.Data.Fold.Window`. We need to also test the functions in case the window is not full. One bug caught: https://github.com/composewell/streamly/pull/2602

Extract the code snippets from the `md` files in docs dir and run `docspec`

1

Create a pipeline that parses out the code and runs the code in `ghci` or uses `docspec` accordingly.

We can use `distributeAsync_` to distribute the incoming ticks to multiple folds. However, in `distributeAsync_`, the consuming folds are statically decided. We need another combinator or modify this combinator so...

- Cleanup the tests - Move module-specific tests into their own modules - Rename the test case functions as we do in benchmarks

The information is currently obsolete. Update it with the usage of `test-runner` instead of `test.sh`

See https://github.com/composewell/streamly/pull/1176