Unfortunately, the layout algorithm had a bug which caused incorrect layout when declaring a union whose lowest-ordinal field was of type Void and nested in an inner union. That is:

    union {
      a :union {
        b @0 :Void
        ...
      }
      ...
    }

In this case, all the fields in the struct after the Void field -- including both unions' discriminants -- would end up misplaced. Although they did not end up overlapping (and therefore the incorrect layout "worked"), the result broke schema evolution rules around "retroactive unionization".

Unfortunately, we must break compatibility with any protocol that happened to contain the above pattern. Luckily, it's a fairly obscure case. Unluckily, Cap'n Proto's own schema format contains such a pattern. Luckily, the use of this pattern was introduced in v0.6.x and therefore has not been in any release build so far.

.gitignore should not ignore bootstrap files, which are not build artifacts. Possibly related to #216.

Fix problem with some RealmGateway template helpers

It turns out that somehow these templates were missing InternalOwner and
ExternalOwner definitions, which was causing problems if a RealmGateway
was defined with them.

Allow setting dynamic AnyPointer fields with a capability

Don't kill the connection just because someone pipelined on a capability pointer that turned out to be null.

Maybe::emplace() should return the newly-constructed value so that you don't have to immediately KJ_ASSERT_NONNULL it.

Fixed installation of schema files via CMake.

Fix Syntax highlighting for Kate/KDevelop

sed -r is a GNU extension, apparently, and due to stars aligning, this didn't break the build, but led to a totally bogus soname on non-GNU systems. Argh.

Apparently most systems (including GNU, undocumentedly) support -E instead, but perhaps the safest thing is to use a basic regular expression. Unfortunately on many systems ? and + are not available in basic regexes, but using * instead happens to work in our case.

Thanks to @neverpanic for catching this.

Fixes #210

Apparently Kate requires the <itemDatas> to be inside the <highlighting>
tag whereas QtCreator also accepts it a level higher.

Tested using this DTD:
https://github.com/jgm/highlighting-kate/blob/master/xml/language.dtd

Fix -Werror build without KJ_HAS_BACKTRACE

This avoids an unused function warning for crashHandler.

Fall back to sysconf(_SC_IOV_MAX) if both IOV_MAX and UIO_MAXIOV are undefined

LocalAddress and RemoteAddress were apparently merged into NetworkAddress long ago.

Fixes a build error on GNU/Hurd.

Fix bug where capability pointers were corrupted when 'transferred', e.g. using adoptWithCaveats() or truncate().

Add ability to construct a new bootstrap capability for each connecting client based on their authenticated VatId.

- Reduce noise.
- Trace through async callbacks.

Allow TwoPartyClient to define a bootstrap interface

Canonicalize NaN on the hppa architecture