22:06:23sveitphoe: thanks for clearing that up. is there some "convention" that one should tend to return 't from the test if the condition type is null/not the type you are signaling?
22:06:58phoethis predicate answers the question "should this restart be visible?"
22:07:31phoeit only gets to use two sources of information to compute the answer: the condition object or lack thereof, and the dynamic environment in which it runs
22:07:46phoeso the answer literally depends on what the restart is supposed to do
22:08:50phoeand whether it should be visible in all cases (when the argument is NIL) or only if specific conditions are signaled
22:09:22phoeand even then, if these conditions have some proper internal state - you can check that by querying the slots of the condition object
22:10:02phoeso, basically - that's a rather generic framework for restart visibility, and usually the answer will be trivial
22:11:22phoefor an example, you don't want to try and offer to save a crash dump file to the default disk drive if you just got a NO-SPACE-LEFT-ON-DEVICE error mentioning that particular disk drive
22:11:47sveitphoe: thanks for the explanation, i think i actually understand the convention now.
22:11:56phoeor, you don't want to try and resend data on a network socket if that network socket just git a CONNECTION-RESET