check_constants makes two kinds of finding and they were treated alike. A value that does not match, or a C name the header does not have, is the library contradicting the package and stops a build the way a permuted defstruct does. An enum nobody mapped and a rule that reaches nothing are about the package's own bindings file -- real, and worth fixing, but telling a lane that added a defenum to go and edit a config in a message shaped like "your layout is wrong" is the wrong thing to fail a build with. Those gate generate-c, where that file is edited. Also: a const prefix now counts as reaching a name before an explicit constant line is consulted, so a rule whose every match is also spelled out by hand is not reported as matching nothing.
Description
Languages
OCaml
67.2%
Emacs Lisp
15.2%
C
10.4%
HTML
2.9%
Standard ML
2.8%
Other
1.5%