libera/#commonlisp - IRC Chatlog

21:23:01 gendl__ Hi, is it true that Bordeaux-threads doesn't have shared read-locks and write-locks, where multiple readers can hold the lock at the same time as long as no writer holds the lock? You'd have to implement those yourself?

21:26:20 gendl__ (i know there's a pretty formulaic way to build readlocks/writelocks given basic mutexes and condition variables)

21:30:14 bike gendl__: as you can see here https://sionescu.github.io/bordeaux-threads/locks/

22:16:30 fe[nl]ix gendl__: that's correct. there's a feature request open: https://github.com/sionescu/bordeaux-threads/issues/77

22:16:43 fe[nl]ix I hope to address it before the release of 1.0

22:21:11 Josh_2 There is book Little Book of Semaphores

22:21:13 Josh_2 Might come in handy

4:11:04 gendl__ fe[nl]ix: https://github.com/sionescu/bordeaux-threads/issues/77#issuecomment-1726829485

4:15:12 gendl__ just made a👆 naive implementation which apparently works for my use case, may or may not be useful as a reference. It's naive because it doesn't do anything about "fairness" and it'd be possible for the lock to get swamped by constant overlapping readers (i.e.in an application where the reader count never gets to zero, a writer might be locked out indefinitely). So some kind of "fairness" heuristic should probably be

4:15:12 gendl__ added.

4:31:28 remexre should I expect writing to the uiop/launch-process:process-info-input of an exited-but-not-waited process to error in some way? unless i'm messing something up, I'm not getting any kind of condition

4:50:17 remexre oh, forgot to finish-output it

6:48:16 varjag i wonder if it's possible to have a json backend for cl-store