Alex Wood

Specifically they give a warning in the REPL, i.e. if they are compiled. The file compiler doesn't seem to complain about it, presumably because before compiling the definition it hits...

sbcl's mechanism for avoiding this appears to be `sb-int:named-lambda`, which not only gives a function a name, but makes that name bound to the function in its body.

The above backtrace is unfortunately not very helpful, since it's just ASDF saying there was an error while compiling, rather than the actual error. (edit: oops, didn't see debug.txt. my...

serapeum-free reproducer attached [test.lisp.txt](https://github.com/clasp-developers/clasp/files/10044677/test.lisp.txt). `compile-file` it and there will be a similar verification failure. The problem appears to be that clasp can't handle the complex type code that serapeum generates,...

I think what's happening is that the `schar` call is being transformed (via `deftransform`) while dead, and recomputing the iblock flow order with dead iblocks around somehow screws things up....

Reproduced. As you said, it's intermittent, and that's due to the occasionally nondeterministic nature of Cleavir. The error is during flow order recomputation during meta evaluation, so I'm going to...

`cl__error` does check for recursion, and all `lisp_error` does is call `cl__error`. So I don't know how you're seeing that.

Sorry for the delay, I have lots of other things to work on. We usually build (and test) on Ubuntu 22.04 (github's `ubuntu-latest`) and MacOS 14 (github's `macos-latest`) with LLVM...

It sounds like the thing we've been hitting where gitlab.common-lisp.net is intermittently down, which breaks the build since koga tries to pull it. Which is a network issue in a...

I've been working towards this again. A few more points. The major blocking issue is, ridiculously enough, debug information. LLVM is pretty strict and will not accept, for example, different...