Dmitry Ignatiev

Finally, here are the docs: https://github.com/Lovesan/bike/blob/master/doc/README.md

@jolby Thanks! The solution is indeed suboptimal, but at least it works

Apparently, there's something going on with NaN on one of the .Net background threads. Maybe inside the GC thread? The following disables NaN-related exceptions on SBCL: ````lisp (sb-vm::set-floating-point-modes :traps (remove...

ECL workaround: `(ext:trap-fpe 'floating-point-invalid-operation nil)`

I have one in my `bike` library https://github.com/Lovesan/bike/blob/master/src/rwlock.lisp It is implemented using bt APIv2 and uses lock and condition variables. It is reentrant (i.e. allows for recursive read and write...

@gendl >What are the practical ramifications of "interrupt-unsafe" ? What I mean by interrupt safety is, basically, lock state safety in a situation like this: 1) Thread A enters one...

Hello! I suppose, this has something to do with compiler macro (mis?)behavior on LispWorks. Although LW is not main development platform(which is SBCL, or sometimes, CCL), i'll see what i...

@quicklisp I was unable to reproduce this. That .NET method exists, so it's kind of strange that the library does not see it. Also, I have not seen anything like...

@quicklisp So, it seems like the method is indeed missing from older versions of .NET, namely from .NET 5 I've backported it to .NET 5 in the latest commit https://github.com/Lovesan/bike/commit/b532f8c96d94e058e1cab091552a3014503794e6...

An SDK update should be necessary because .NET 5 is out of support now. Still, .NET 6+ has this FP issue on Linux. Maybe I'll incorporate the existing workaround into...