Apply the emphasis and code mark up separately
ReadableStream: Make [[enqueue]] throw when draining

Fixes: #166
Upgrade Traceur
Initial draft of benchmark suite (#120).

This is meant to allow us to assess the impact of a spec change on the performance of the algorithms via the reference implementation.

This initial draft contains a decent amount of dead code from abandoned ideas that will be cleaned up in the subsequent commit; however, I thought it'd be useful to have it in source control in case someone wants to use it later.
Remove dead benchmarking code.

There were ambitions of displaying nicely-formatted renderings of the params being tested, and thus code was included for that. But right now it's looking like that's not going to be that important, so remove it.
Add a recording-runner for the benchmark.

This records the results to a file on disk, so we can compare between snapshots.

While doing this, factored out the runner code to support both use cases.
Add something that diffs your recordings and shows the results
Add a README for the benchmarker
Fix wait() on a just-started stream to fulfill immediately.
Small test tweaks

These do not affect the tests, but just improve clarity or similar.
Touch-ups to the benchmarking code

Based on @tyoshino's comments on #170.
Remove only from a test in test/pipe-to.js

Seems accidentally committed
Add a spec for an extended API for binary data handling
Fix slightly-broken test

(On Node 0.11 at least, `Uint8Array` requires `new`)
Follow up change for #173

Addresses comments by @domenic at
https://github.com/whatwg/streams/pull/173#issuecomment-53059246
Use RegExp for test.throws()

throws() expects the "expect" argument to be a RegExp.
Show how too many writes in a row causes stack overflow

This test fails currently due to recursion between signalDone and [[advanceQueue]].
Change underlying sink write to be promise-returning
Use boolean [[writing]] flag instead of [[currentWritePromise]].
Add test to show why the state check is necessary.