Harendra Kumar

Throw a specific exception in deserialize failure

3

Currently we just call `error`: ``` if (next >= \val -> pure (next, val) else error $ "deserialize: accessing array at offset = " ++ show (next - 1) ++...

fromPtr, fromBytes in Array module should be monadic

1

Otherwise we may create a lazy thunk which is evaluated later and we might be using a stale pointer.

Rename MutArray APIs to follow naming conventions

1

``` castUnsafe => unsafeCast newArrayWith => emptyWithAligned getSliceUnsafe => unsafeGetSlice createOfWith => createWithOf (argument order convention) putIndexUnsafe => unsafePutIndex modifyIndexUnsafe => unsafeModifyIndex getIndexUnsafe => unsafeGetIndex realloc => reallocBytes reallocWith =>...

Add array conversion to and from foreignptr

1

Introduce something like `toForeignPtr` and `fromForeignPtr` so that we can implement the `toArray` and `fromArray` in streamly-bytestring.

catRights, catLefts behavior

1

`catRights` should produce error if it encounters `Left`. We can use `catRights_` for discarding `Left`s.

Many of the fold functions in Data.Fold should actually be scans in Data.Scan.

Use the Path type in the File module

1

* Copy File module to FileIO, remove the deprecated functions from FileIO. * Change FilePath to Path in FileIO. * Deprecate the old File module

In `Streamly/Internal/FileSystem/Event/Linux.hs` we convert the OS paths to and from String to use the FilePath APIs. We need to remove the usage of these and the representation of paths using...

It does not make sense to use a non-terminating fold/parser in an applicative/alternative/monad composition. It would be nice if we can identify this and produce a warning. Theoretically, we can...

We need to keep track of the context e.g. position in the stream or line numbers in case of text processing, and report it when an error occurs.