18:53:27phoeIt is horrible - I am interfacing with C.
18:54:07phoeBut it looks like I can compress and decompress arbitrary Lisp uint8 vectors, which is good.
18:55:38phoeThe best part - I needed to build the .so library for Linux myself because the original LZMA makefile from Igor Pavlov only builds binary executables.
19:34:04phoeit's pretty good, and what cl-autowrap provides is also very good to work with
19:34:39phoethe header files for LZMA got parsed automatically and I got all the required C functions, types and sizes automagically
19:35:49phoebut I spent whole two hours debugging an issue that size_t was eight bytes where I only allocated four - and boom, heisenbugs, image corruptions, drops to LDB and such fun stuff.
19:36:10phoethe stuff that does not exist in Lisp because you don't need to allocate raw memory.
19:36:31phoeso it's less of CFFI being terrible and more of the C land being very primitive
19:39:28phoebecause I thought that I should allocate four there as size_t wasn't called size_t in the original code but had some quirky typedef that made me assume it's four bytes.
20:50:55Baggersotwieracz: does bt:interrupt-thread work? also is it your thread and do you have an idea of why it might be blocking? Where a blocking call is needed it could be worth looking for a similar function with a timeout
21:16:51reglbut I got one failure in one of the files
21:17:23regldebugger invoked on a UIOP/LISP-BUILD:COMPILE-FILE-ERROR in thread #<THREAD "main thread" RUNNING {10031A63F3}>: COMPILE-FILE-ERROR while compiling #<CL-SOURCE-FILE "cleavir-environment" "compile-time">
6:10:25axionDoes anyone happen to use company-mode in common lisp code buffers? I am trying to switch from auto-complete, but it seems to only be working in the repl mode. I would be interested in checking out someone's emacs config if it's no trouble.