iopipe v0.2.0 - safe update

aberba karabutaworld at gmail.com
Mon Jun 29 00:37:20 UTC 2020


On Sunday, 28 June 2020 at 20:26:43 UTC, JN wrote:
> On Sunday, 28 June 2020 at 18:57:22 UTC, Steven Schveighoffer 
> wrote:
>> Just wanted to post that I finished my update of iopipe to be 
>> @safe. I still have some work to do with std.io so things are 
>> more usable (next on my list is to make standard handles 
>> accessible).
>>
>> In this update, I've made it so nearly all of iopipe can be 
>> used in @safe code. The one exception is the RingBuffer, which 
>> can leave dangling pointers, hence the unsafety.
>>
>> Inside iopipe is a RefCounted type that is @safe. It uses the 
>> GC for memory management, so while destruction is synchronous, 
>> the memory itself is left to the GC to clean up.
>>
>> -Steve
>>
>> https://code.dlang.org/packages/iopipe
>
> What's iopipe and what does it do? How does it compare with 
> std.process?

I my line of words, its what you'd use to stream large files and 
do processing on it. Like CSV, video??, Json, and the like. Its 
high performance cus it optimized to haven great performance even 
for large files. Designed to let you chain the processing 
pipeline using reusable functions...and  you can compose one 
yourself.

I'm curious myself how it differs from the NodeJs Stream API. 
Would you say iopipe is a Streaming API by definition?


More information about the Digitalmars-d-announce mailing list