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

Update obsolete comments.

Fix incorrect, confusing comment.

Add missing keywords "override".

https://llvm.org/bugs/show_bug.cgi?id=22354

At the time DisallowConstCopy was introduced, GCC 4.7 and Clang 3.2 refused to allow the non-const copy constructors to be defaulted inline. This must have been concluded to be a compiler bug, as GCC 4.8 and Clang 3.4 seem fine with it. So, we can clean this up.

Meanwhile, the above-linked Clang bug triggered when a DisallowConstCopy derivative is captured by value in a C++14 generic lambda. capnp::CallContext in particular tended to be hit by this a lot. The bug only affects non-default (or out-of-line default) copy constructors, and thus is conveniently sidestepped by this change.