Our great sponsors
-
That thread is not complete context; see also e.g. https://github.com/edicl/cl-ppcre/pull/30 and https://github.com/edicl/cl-fad/pull/24.
-
Context: https://github.com/edicl/flexi-streams/issues/25
-
SonarLint
Clean code begins in your IDE with SonarLint. Up your coding game and discover issues early. SonarLint is a free plugin that helps you find & fix bugs and security issues from the moment you start writing code. Install from your favorite IDE marketplace today.
-
That thread is not complete context; see also e.g. https://github.com/edicl/cl-ppcre/pull/30 and https://github.com/edicl/cl-fad/pull/24.
-
That's what modern ASDF attempts to do, e.g. with package-inferred systems - system definitions are based on reading DEFPACKAGE and UIOP:DEFINE-PACKAGE forms without executing them. Still, that depends on people having standalone DEFPACKAGE and UIOP:DEFINE-PACKAGE forms that aren't e.g. generated by MACROLET or SYMBOL-MACROLET which famously require code execution for the forms to be created - and even I wrote code that uses macros to generate package forms.
-
I can point to my patch which is actually from 2018. Often I just fix things for myself and don't report to anyone else (maybe remark on IRC sometimes when relevant), but in this case, it obviously wasn't just me who had issues with these warnings: just look at the threads under discussion. At some point they got added and systems which worked for years got "broken". It wasn't stassats who broke them, it was ASDF. Patches for some of them were written to "restore order", and stassats chose not to merge them.
