freenode/#clasp - IRC Chatlog
Search
18:43:50
Bike
cos what check-type does is the typep, but then it signals an error that can be restarted by modifying the place
19:49:17
drmeister
I think every argument processing error will now print the function name in the error message and lots of warnings in the C++ compilation and cclasp compilation have been eliminated by fixing their underlying cause.
20:24:27
drmeister
I spent the whole day improving the debugging experience and now all I want to do is code with it but I have to go to a dinner party! ARGH - life is just not fair sometimes.
20:29:23
drmeister
Anyway, I'm feeling pretty good about things. I really like these function-description objects embedded in the llvm Module's - they solve problems I've had from day 1.
20:54:22
drmeister
Do you know what this means? It's the longest meaningless error message I have seen in a while.
20:55:23
drmeister
I don't know what other ASDF it's getting and where it's getting it from or where it is stored.
21:03:29
attila_lendvai
drmeister: in short: you have a very old ASDF somewhere that the running ASDF can see in its configuration
21:04:26
drmeister
Hmm, this is just happening in my docker build - maybe I'm cloning another asdf in the Dockerfile.
21:06:25
attila_lendvai
it's a very old ASDF. it's most probably coming from the cl-asdf debian/ubuntu package... is it installed? maybe as a dependency of something? (note: the cl-foo debian packages were an endless source of headaches about 5-10 years ago when I gave up on them completely)
21:08:06
attila_lendvai
drmeister: it can happen on some old ubuntu or debian, but it's not happening recently... on debian stable I have the sbcl package but none of the cl-foo
21:08:40
attila_lendvai
quicklisp also has a ridiculously old ASDF, but that shouldn't be visible to ASDF
21:08:55
drmeister
I'm pulling down the docker image now - I'll crawl into it once it's down and see if I can find anything.
21:10:42
attila_lendvai
drmeister: keep in mind that it's just a warning... maybe you can just ignore it? :)
21:11:14
drmeister
I have been - but for the past couple days I've been fixing warnings because they irk me.
21:15:56
attila_lendvai
if that helps I can bug Fare to make it shorter... :) jokes aside, running free of warnings is a good idea. (which doesn't mean 100% if the cost is too high for the last 1%. and disabling non-useful warnings is also allowed... :)
22:01:11
karlosz
is it legal to compile in the fdefinitions of any symbol in the COMMON-LISP package?
22:05:12
karlosz
like, normally with (f x y) you'd emit code that first looks up the symbol function
22:09:36
Bike
in like, sbcl, if you compile a function, sbcl will derive the type and use that in other functions in the file, i think.
2:56:17
drmeister
I lost backtraces in jupyter lab in the new docker image because I used the quicklisp version and not our local-project implementation ... rectifying...
4:36:02
drmeister
You commented out inline.lisp and you could build cclasp - but asdf had a problem.
4:37:46
Bike
i don't really have a concept for what the problem could be. it's pretty rare to be able to build the whole of clasp and then hit a problem just with asdf
4:40:31
drmeister
It's happened to me several times. I have often built clasp and then failed when building or running one of those. Not for the reason you are seeing.
4:42:49
drmeister
I'm worried that it is the inlining criterion. This inlines local functions - could it be a recursive labels function?