The API reference, the requests page and the internals say that each
exported function declares its arguments' full types, which SBCL checks on
entry and at compile time where it can. destroy-proxy takes any proxy
but a display, and the errors page shows the type-error a display now
gets in place of the wl-error. The testing page gives the new count.
The internals page names the internal functions as cl-wl now does,
without the % prefix: info-interface-pointer, send-request,
dispatcher, deliver and call-handler.
The API reference says that proxy-display has no writer and that
define-request refuses, as it is expanded, a request it cannot define.
The scanner's page calls shipped-protocols and shipped-array-elements in
place of the old variables, and names the new cases of protocol-error.
The errors page lists the new wl-error cases, among them an array event
of the wrong length and misuse of the test compositor, whose page says
so too. The internals page describes the read step that dispatch and
read-events share. Home's example gives every package a local
nickname, as the README's does, and Getting Started recommends that.
The raw layer page loses wl-proxy-marshal-array-flags/address: the
marshal function itself is inlined now. The requirements and the
platform page name SBCL alone, the suite's result is for SBCL 2.6.9, and
the test commands, CI, the scanner and the allocation notes no longer
mention CCL.
Follows cl-wl 3cb259f: the raw layers are on cl-ffi, errno and pointers
to addresses come from it, so cl-wl/sys is gone, and getting started
lists cl-ffi in the qlfile beside cl-wl.
