Make .end() behave like stream.end() ?

Hi,

Highland.js .end function doesn't accept parameters, and just closes the stream, unlike stream.end, which accepts 1 parameter of data, send it, and then closes the stream.

Does it make sense to change highland.js end function to be more like node end function ?
I am building a lib, which provides it's users "smart" stream (e.g. highland streams), but end is not behaving the same.

Start at Highland.js's .end entry point and compare its current behavior with Node.js stream.end, especially how data is accepted before closure. Define and test the intended parameter and shutdown semantics; done means Highland streams provide the agreed stream.end-compatible behavior without ambiguity.

Written by the indexing model from the issue text.