Masataro Asai

it does not search through all functions in the lisp image. It checks only 3 functions, namely `-`, ``, ``. Most usecases of `defstruct` falls in the first case. The...

I also understood the need for specifying particular function naming scheme. Perhaps through compiler option (I mean special variable) or by adding a specialized version of the structure pattern.

Oh I forgot to note ( and the fact itself ) that it is able to disable this new scheme through `(defvar *arity-check-by-test-call* t)` --- so `(setf *arity-check-by-test-call* nil)` suffice.

your idea on `(structure ( (:conc-name )) ...)` sounds good, and perhaps I can implement it without affecting the compatibility.

Also I would convert `style-warning` to `simple-condition`. That would not cause quicklisp to reject the project while still printing the message.

regarding `trivia.optima-compat` --- perhaps its time to move to version 2?

At least I made the style warning more verbose. a5a091b

At 54ddc5c7c8915e3f486ca57df34997007b3809c9 , the style warning is shown only once after the library is loaded. This should reduce the annoyance in the most common use cases.

See type-r

It is part of type-i so the issue should go there