Adithya Kumar

`FileSystem.DirIO` has functions with `Path`. But, `FileSystem.File` uses `FilePath`. Because of this, there is an unnecessary conversion from `Path` to `FilePath`. We can remove this once `FileIO` is introduced.

`readDir` APIs with the default config should have the same behaviour on both `Windows` and `Posix`. The default behaviour should be: - Don't follow symlinks - Don't ignore any errors

Limit the number of open fds in recursive directory traversal to a defined value

1

A lot of open FDs cause the flow to fail with: ``` uncaught exception: IOException of type ResourceExhausted benchmark-tmp/dir-structure/dir_4/dir_3/dir_2/dir_5/dir_5: openDirStream: resource exhausted (Too many open files) ``` This is true...

All options of the `Config` do not affect the `Channel`

1

The stopping condition of the stream is baked into `concatMapWithChanKGeneric` depending on the `Config`. If one simply creates a `Channel` with `StopAny` and sends streams to it, things won't work...