Looks like a disagreement between fixed capnproto code and clang 4.0. There's possibly nothing Mir can do to fix it.
Looks like a disagreement between fixed capnproto code and clang 4.0. There's possibly nothing Mir can do to fix it.