Follow cl-vk cb47a8c: the types of the enums' keywords
The pages on structs, the generator and the packages say that each enum's
keywords are a type of cl-vk/structs, named as the structs are, VkFormat's
being vk-format.
The API reference describes the types object and extent, the ranges of
version, and what raw-handle and adopt-surface refuse. Errors and the
generator's page say that SBCL checks the declared types on entry, and
warns when it compiles a call with a constant of the wrong type.
Describe cl-vk's conditions for misuse and its escape hatches
Misuse is a type-error where check-type can say what is wrong, and a
vk-error with a message otherwise; the struct macros' expansion-time
errors are vk-errors too. instance-commands, device-commands and
swapchain-images are escape hatches that refuse destroyed objects, and
swapchain-images has an entry of its own. device-queue takes :family
and :index. with-structs takes a foreign pointer for a field that
points to untyped memory. The generator no longer has *platforms*.
The requirements name SBCL alone, the platform page describes cl-vk/sys
as what cl-vk takes from SBCL, and the test commands and the generator's
reason for laying out its output by hand no longer mention CCL. The
allocation claims drop their "on SBCL".
Follows cl-vk cae101e: the raw layer's structs, types and the loader's
library are cl-ffi's, the examples use cl-ffi's operators, and getting
started lists cl-ffi in the qlfile beside cl-vk.
Add the reference pages and the sidebar; document enum keyword rules
Add API Reference, Errors, Lifetimes and Threads, Raw FFI Layer,
Generator and Registry, and Platforms and Testing. State the full rules
for enum keywords, including the prefix word kept before a digit
(:type-2d), and use :type-2d in the image view recipe.
