The idea was to have a little playground using the packages we developed. But it didn't really turn out to be useful.

Since we're just parsing an integer we can just try to parse the next token from the lexer, like how we parse the playlist version.

We'll need it later and we're a few nested for loops and if stmts down so a little cleaner once we do this a few more times.

Now we handle the tag header parameter, and all the different forms the values of To and From can have.

duh

Not ready... if ever?

Parsing the base and extension ticks of the PCR was actually incorrect. Whilst we were consistently storing and decoding values, they were incorrect values. This patch adds tests which concretely exposed the bug spotted by @kevmo314. Thanks again!

Fixes the base calculation by removing the 7 rightmost reserved and extension bits.

It's an optional field, but aucat(1) from OpenBSD creates files with this field populated so I feel like it may not be that obscure in the wild.

We can create it when we want to create it. Think this was accidentally added by me, sorry!

Because it’s a distinguishing feature of the project!

Resolves: https://github.com/untangledco/streaming/issues/29

Use Go's io.Reader and io.Writer so that we don't have to keep everything in memory, and it works in a way that Go programmers are familiar with.

Big Buck Bunny is the classic test sample for a lot of video dev work. tos.m3u8 is here because it is a valid playlist containing lots of comments and empty lines. Unusual, but still a valid playlist; hoping it will help catch bugs in our parser's handling of comments and whitespace.