More formal and less personal reference to the VLAD flow analysis.
Less personal reference to Sussman's pattern matcher.
Add and document lambda-case*
Arrangement and subdivision.
Mention, if not discuss, other pattern matching facilities I know
about.
A test that macroexpansion and procedure integration lead to the
desired code.
The second example works too, but is something of a surprise.
The last two examples from pattern-matching-test.scm.
Clarity.
These thoughts I had while hashing out the implementation have
outlived their usefulness.
Oh, that's why it was running out of stack: I had forgotten that the
unless macro was only defined in the larger project this is taken
from.
Abstract the number of repetitions.
Benchmarking is hard: you want it to take enough time to get good
measurements, but you want it to run fast enough to be part of the
development suite.
Clarify.
Explain difference of naming convention.
Rename source files to avoid claiming the name "matching", since this
project is called Pattern Case.