Adithya Kumar

@Diamondy4 You can probably play around with timestamping the required input, making timestamp a first-class citizen in your stream, and folding it according to your use case. For example, ```...

> maybe as background check every X seconds You can do that with the suggested method. Data in (mid) processing will always be lost if you want to end some...

Push `primitive` dependent modules to `streamly`.

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

Closed in https://github.com/composewell/streamly/pull/1772

Pushing this to the next milestone. This looks like a breaking change.

1. Rename the Unboxed APIs properly. 2. Rename `ArrayContents` properly readByteArray -> peekWith writeByteArray -> pokeWith ArrayContents -> Memory or Storage or OAM (Offset Adressable Memory)

Common API naming: - `newAligned` - `getInternal` - `cast` - `reallocAligned` - `asPtrUnsafe` - `putSliceUnsafe` - `cmp` We should not expose internal details. Any common internal manipulating APIs should be...

The module should be renamed to `Streamly.Internal.Data.MutableByteArray`

Closed in https://github.com/composewell/streamly/pull/1772