freenode/#sbcl - IRC Chatlog
Search
10:24:17
luis
Unless you're on Windows, in which case stack overflow blows everything up on the first try. :-)
10:35:50
flip214
I'd love to have atomic GF/method updates, so that redefining a method on a busy server doesn't ever give "There is no applicable method for the generic function ... when called with arguments ..."
10:39:44
flip214
luis: well, there was an applicable method which got redefined - so if the GF dispatcher function would be changed atomically it wouldn't break
20:11:33
Krystof
I suppose it would be possible to imagine an atomic replace of a method if there are no specializations of add-method and remove-method
21:58:24
mfiano
Quick question: Would it be conforming for SBCL to emit a note/error/whatever if the default value of a struct slot does not match its type? Currently, this is only checked at instantiation time, for example, this compiles cleanly (defstruct foo (x nil :type fixnum))
22:02:45
mfiano
Well, again sourceforge's search fails me. I'll just accept that it is like this for a reason.
22:05:22
karlosz
mfiano: the gist of the debate was about how it's hard to leave the default value of a slot unspecified while specifying a type and making everything type-safe
22:06:01
karlosz
also related was the issue of what to do with the default values of (defstruct foo x y z)