Add range input device

When given a range of elements, or a range of slices of elements, you can form a buffered iopipe out of it using the new rangeDev wrapper.

This allows easy use from anything that provides a range interface.

Minor bug fix

Merge pull request #38 from schveiguy/fix87

Fix #87

Make delimitedText work again.

Fix issue #32

Fix io dependency

Remove version dependency on io. Any version is fine, as it's optional, and the deprecated portion of iopipe that depends on it doesn't depend on any older API.

Fix issue with stray @safe tag

See #31

Everything is safe!

Aside from RingBuffer, everything can now be done within @safe code.

Minor update to buffering

To assist in using iopipe as an output string buffer, this makes the default buffer size small for null streams, so we aren't preallocating a huge buffer for what is likely a small string.

Add writeBuf mechanism for output

Over and over and over, I was writing local functions that do what this thing does -- write data to the front of the window, and release it, extending when necessary.

This facilitates greatly the concept of writing data to an iopipe. Should only be used on iopipes that have a buffer that is processed after release, or where you are writing to a piece of memory (i.e. an array).

Fix issue with unzip and `immutable(ubyte)[]` source pipe

v0.1.4

Cast no-side-effect function to void when source is immutable array.

Add valve support to delimitedtext

v0.1.3

Merge remote-tracking branch 'origin/master'