Parse

[articice]

Hi!

I've added two methods - parse and rest.

parse is taken by analogy from node-binary but still keeps this module's code small, neat and clean. It is essential for TCP framing in a stream parser. It can be useful for defining strict boundaries for data segments inside a frame or a stream (although I didn't do it in my application).

rest is an important improvement, that does not exist in node-binary or dissolve-chunks. It allows the user to cut the rest of the frame without explicitly tracking current parsing position (and needed length). Of course, frame length is defined by the length of a previously sliced static buffer, but if the internal parsing routine is complicated enough (see simplified real-life example), keeping track of buffer length left is tedious; while dissolve does not export a "parser position" property, and personally, I think it should stay this way. In my example, rest allows cutting out non-terminated or EOM terminated strings of "unknown" lengths (in the last data segment for a parsing loop inside a data frame).

dissolve-chunks, while having an interesting approach to parsing data segments (they call it "chunks"), unfortunately, only relies on fixed length known beforehand.

[articice]

Oops, I've entirely missed that this module has mocha tests part and CI checks based on it.
Will work on tests, pushing onto this branch.