14:32:01hayleyThe existence of compiler notes is implementation dependent already.
14:32:54hayleyBut (deftype silly-condition () '(and condition (not serious-condition))) is useful.
14:33:39jackdanielsome conditions are not silly though! signaling partial results in an otherwise synchronous body is one example
14:34:27NotThatRPGhayley: Yes, it would be nice if one could make code that wraps around compilation, that could portably handle different implementations' equivalent of compiler notes (assuming that these are implemented as conditions of some sort).
14:35:13aethjcowan: no, but afaik (based on another IRC channel anyway) Fedora would move exclusively to xwayland
14:40:44Bikeshinmera and i have been talking about doing that, notthatrpg. it would basically be ripping out part of swank. i think my main conceptual confusion now is why sbcl "compiler errors" aren't actually errors
14:41:02Bikealso i'll have to check if any implementations have a compile that never signals and only reports problems some other way, which would be annoying
14:41:43NotThatRPGBike: if you were to do that, I'd be interested in porting it into UIOP...
14:46:07Bikei will see what i can do. i'm doing a bunch of other stuff for clasp at the moment, though
15:25:00Bikeallegro has a compiler-note class but swank at least treats it as unexported. the abcl code looks like you have to bind an internal dynamic variable to make the compiler actually signal warnings. geh.