Search
23:01:02
frgo
oleo: most likely; rm -rf ~/.cache
23:01:25
frgo
but beware: this is a dangerous command.
23:05:05
oleo
i already told that it does not change anything
23:05:25
oleo
there's nothing else referencing the old link
23:06:29
oleo
my .config/common-lisp/source-registry.conf.d/blah.conf contains also no :dir nor :tree that could be inadvertently captured
23:13:37
oleo
(push (qmerge "quicklisp/") asdf:*central-registry*) now i see why
23:13:50
oleo
probably cached by quicklisp
0:44:14
karlosz
sweet! i have (lambda (n) (dotimes (i n) (print i))) compiling to an executable clisp function all the way through. and it works!
0:45:23
karlosz
is there no generic function for the user choosing which hir transformations they want to apply?
0:45:48
karlosz
instead of writing like clisp-hir-transforms (inst)
0:47:44
Bike
the specialization would be basically equivalent to writing the function anyway
0:50:41
karlosz
true. though there are other generic functions which take parameters like implementation and system
0:50:46
karlosz
which are meant to be specialized?
0:50:51
karlosz
but are mostly nop in practice
0:51:46
Bike
they don't do whole behaviors though
0:51:54
Bike
stuff like convert constant to immediate is pretty simple
0:52:48
karlosz
yeah. i guess i still don't have very good instinct for when a function *should* be generic or not
1:17:47
drmeister
Good job karlosz!
2:02:25
DVSSA
drmeister: whats the slacks url?
2:06:04
drmeister
I sent you a message