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 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.
Follow cl-wl 4f0e504: five more protocols, cursors, pipes and borrowed proxies
Protocol Bindings describes tablet-v2, cursor-shape-v1, text-input-v3,
pointer-constraints-v1 and relative-pointer-v1, and the new Cursors page
cursor-shape-v1 and cursor themes through cl-wl/cursor. The API
Reference adds BORROW-PROXY and the pipes, MAKE-PIPE, RECEIVE-TEXT and
SEND-TEXT, which Requests and Events introduces and a clipboard recipe
uses; it was run against the test compositor. The raw layer, errors,
lifetimes, allocation, the scanner's protocol list, the requirements, the
test count and CI follow.
