libera/#commonlisp - IRC Chatlog
Search
21:47:05
phoe
in practice everyone seems to fall back to what old lisps did, with also a warning from SBCL
0:14:53
nij-
Hi! Is it possible to handle a condition by popping out the choice panel to the user for N seconds, and close the panel to do something else if no choice is provided?
0:22:30
Bike
nij-: that would have to be a feature of the debugger. i do not know of any debuggers that do that, but you could write one.
0:34:26
nij-
Perhaps this is an XY problem. I want to let a lot of threads running in the background. But I find it annoying to have a debugger popping out everytime a condition is met.
0:43:11
Bike
having a debugger disappear while while i'm deciding what to do would probably just piss me off
2:25:32
hayley
stylewarning: For no good reason whatsoever, here is Coq compiled to CL <https://plaster.tymoon.eu/view/3637>
2:49:58
hayley
By doing really crappy compilation of the JSON output of the Coq Extraction module. I suspect Coalton would generate much better code (mostly around munging Lisp-1/2 and FFI'ing curried functions to Lisp uncurried functions).
2:50:40
hayley
As for why, because one course this semester involves "using static analysis tools" for cloud stuffs, for which they probably mean a linter.
2:51:48
hayley
Then I had the terrible thought last night to feed verified code to CL. Not that my compiler is sound, or even close to working for anything other than ADD.
6:58:08
hayley
stylewarning: Do you have any opinions on if/how to expose curried functions to CL? I think I can glean how much to uncurry from the Coq JSON dump, but the idea of gleaning it puts me off a bit.