Fix issue where entire (very long) input is passed to bitSeq.

[theqabalist]

So I need help writing a test that actually creates the problem I have fixed. In the binary parser I have constructed, when the parser runs, I am getting the entire input to bitSeq, when it's supposed to just operate on a slice of the input (when embedded as part of a large parsing context). I have fixed this issue, but I cannot seem to replicate it in a small test to prove it's an issue.

Can someone help me construct a proper test that will fail without this change?

[coveralls]

Coverage remained the same at 100.0% when pulling 8eb1966 on theqabalist:fix/bit-seq-wrong into c1e28fb on jneen:master.

[theqabalist]

I was actually just being [redacted] yesterday and didn't think through my input buffer properly when constructing the test. I have a properly failing test case now to prove the problem.

[wavebeem]

Looks good. Glad you were able to figure it out. I didn't have a chance to look at it yet but it all looks sorted now.

(p.s. please consider not using exclusive language next time)

[wavebeem]

I forgot to mention that I released this as 1.7.1 shortly after merging the PR