13:37:46atgreenSBCL team said "that's what you get" when you use (safety 0). The cl-postgres maintainer accepted my patch.
13:43:12aethIs anything other than (speed 3) ever useful to write in code? I mean, code you give other people. Because (speed 3) sometimes makes the compiler go down another path (one that perhaps might be too slow to compile with when compiling on a 386 or whatever) that generates better code in a useful way...
13:44:27aethAnd in SBCL it even gives you optimization notes (sometimes too many, if the optimization note is 'try dividing by another, nicer number') so it's kind of useful to keep contained to where it's needed instead of all over the program
13:54:36aethUnless you #+sbcl it's a general thing.
13:54:58aethMaybe (compilation-speed 0) is very useful on ECL or CCL, who knows
13:55:53aethBut compilation-speed and space seem to be something that an implementation might reasonably not care about at all in 2022.
13:58:14aethI wouldn't be surprised if some (safety 0) issues are from people who use other implementations and don't realize just how dangerous it is on implementations like SBCL that believe you when you say you want no safety.