Avoid deleting temporary FASL files?

[fosskers]

I just noticed that if I manually type this into a REPL, where foo is a system from my project:

(asdf:load-system :foo)

that FASL files are produced / loaded from my ~/.cache/common-lisp/. However, if I use sly-asdf-load-system, it produces lines like:

; wrote /home/colin/.cache/common-lisp/sbcl-2.4.9-linux-x64/home/colin/code/common-lisp/aero-fighter/src/main-tmp1CXFJSK9.fasl

And then these FASL files seem to be immediately deleted after loading, gone from the filesystem. In particular this forces a recompile the next time I load up the REPL. Is there a way to disable this behaviour, and have it cache the FASL files like a normal call do load-system would?

Note that the above output was from SBCL, but with ECL as well I notice it insisting on fully recompiling every file in my project (across multiple systems) when I use sly-asdf-load-system.

Thank you.

[aadcg]

Is there a way to disable this behaviour, and have it cache the FASL files like a normal call do load-system would?

@fosskers, among the arguments that asdf:load-system takes, you'll find :force and :force-not. These manage the cached FASL files.

sly-asdf-load-system (which calls asdf:load-system) violates the default value of the :force argument to t and the conclusion follows.

I find it bewildering since it breaks the principle of least surprise. If these are REPL shortcuts, shouldn't they map to the behavior of typing them? sly-asdf-load-system is indeed quite opinionated (see also my observation at #42 (comment)).

---

I think that the default value of :force should be honored; one universal argument would set it to t; and two universal arguments would set it to :all.

Note, however, that sly-asdf is basically slime-asdf, and it is unlikely that they're open to change. This contrib may be useful for some but, for the above, I don't use it.