Such values are not allowed by the JSON spec. We match the behavior of
JSON.stringify in Firefox and Chrome.

fixes https://github.com/sandstorm-io/capnproto/issues/261

Fix some documentation typos.

Fix typo in documentation

Add TextCodec to expose an API for the schema's text format.

Spellcheck the styleguide

Typo found by @mquandalle

Mentioned three days ago, didn't want it to get forgotten

Fix typo in two party RPC docs

Make sure ArrayPtr<char> stringifies the same as ArrayPtr<const char> (without commas after each character)

Use ip4 sockets for wildcard on OpenBSD

Short-term fix for #220.

Fix typos.

Added method accept() to TwoPartyServer for servicing arbitrary AsyncIoStreams.

Increase arenaSpace to fix 32-bit builds.

Fix bug in JSON encoder that caused each byte of a UTF-8 sequence to be escaped as a separate character.

Added capnp::TwoPartyServer::accept(...) this method allows capnp::TwoPartyServer to service arbitrary kj::AsyncIOStream objects such as those representing two-way pipes (socketpairs).