Yes, this is a feature, not a bug. If you change the ASD file, ASDF has no way to know whether any compiled file in the system is up to date. For example, you could have added a system dependency that brings in a new use-package relationship and a macro, or reader macro that invalidated every compiled file.
> On Jul 16, 2018, at 05:02, Chun Tian (binghe) <binghe.l...@gmail.com> wrote: > > Hi ASDF list, > > I have some huge generated Lisp files which took a lot of time to compile > into fasl files. I put the sources into my ASD system definitions with other > hand-written Lisp files in parallel (thus no dependencies at all). > > I found that, whenever I changed the ASD definition, if I load the system by > ASDF:LOAD-SYSTEM, all Lisp files will be recompiled, even their source files > are not changed at all. > > Is this a desired feature or possible issue? Do I need to provide sample code > to show this “issue”? I’m using quite a recent ASDF (version: 18.104.22.168) > > Regards, > > Chun Tian >