2:56:17drmeisterI lost backtraces in jupyter lab in the new docker image because I used the quicklisp version and not our local-project implementation ... rectifying...
4:37:46Bikei 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:31drmeisterIt'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:40:51drmeisterBut they stress the compiler in different ways than clasp source does.
4:41:04Bikeprobably mostly because asdf does everything in eval whens
4:42:00drmeisterWell, we won't know until you narrow it down to the bad form.
11:18:29kpoeckDrmeister: I would like to fix interpret_token_or_throw_reader_error to allow all possible float-types in _STARreadDefaultFloatFormatSTAR
11:24:18drmeisterNo DoubleFloat and LongFloat are the same. I've toyed with the idea of using the GMP infinite precision float for long-float.
11:24:55kpoeckStill puzzled with SingleFloat is read with strod, since clasp_make_single_float is defined to accept a float and is passed a double
11:25:32kpoeckok, than regarding LongFloat the fix is obvious
11:25:46drmeisterShortFloat and SingleFloat are also confused - SingleFloat is a tagged C 'float'. I think (but I may have forgotten) ShortFloat is still managed by the GC.
11:26:51kpoeckShortFloat is allocated by GC_ALLOCATE(ShortFloat_O, sf);