lisp-critic
lisp-critic copied to clipboard
g000001
The Lisp Critic scans your code for instances of bad Lisp programming practice.
There is a legit use for `progn-single-form` which appears quite often with `unquote-splicing` (or `eclector.reader:unqote-splicing`). Maybe its more appropriate to not give the critic in this case?
A new rule check-prefix was added [6 months ago](https://github.com/g000001/lisp-critic/blame/ea19f82a168a6119ac1b10d0f457c01a7119602f/lisp-rules.lisp#L803). However now it produces too many warnings on all my projects where `check-type` function is used to ensure contact on input...
