9:53:53luisLooks like stuff in read-only space also likes to raise SBCL_BREAKPOINT_EXCEPTIONs.
10:50:18luisbug-936304.impure.lisp takes forever to run
10:52:08luisah, yes, because I've got a 30 GB dynamic space
12:35:25Krystofit's not the size of your heap that matters, but what you do with it
12:35:54Krystofby the way: on the second train journey I took this year, my train was cancelled because a train didn't get to the depot on time. Can I blame you?
12:39:14flip214Krystof: that's just anecdata. come back if you have at least a thousand measurements, so we are able to do p hacking.
14:49:04lukegoACTION idly wonders if there could be a cottage industry for algoritms that scan the heap sequentially, even in multiple passes, to make use of the ~15GB/s bandwidth for independent reads
14:49:52lukegothough I guess pkhuong is a leading authority on parallelizing memory accesses so probably any low hanging fruit has been picked :)
14:59:08luisKrystof: was the train run by London Underground Limited?
15:03:43luisIn any case, I'm happy to report that LUL is running SBCL in their production environment, so there is potential blame to share in the future.