freenode/#sbcl - IRC Chatlog
Search
9:55:12
Xof
well the logic about "can't change behaviour with optimization settings" is true if the code in question is conforming
9:56:47
Xof
I mean, if McCLIM currently has code that looks a bit like a pfdietz test case, that might also be a problem :-)
9:57:26
jackdaniel
https://files.mastodon.social/media_attachments/files/009/933/331/original/ee68293b48ba16c6.png (and it is not a bug! :)
10:35:13
jdz
Just run into a problem: compiling a method that calls the GF it belongs to does not warn about invalid number of arguments. Example: (defmethod test (a b) (test 42)).
11:01:56
scymtym
seems like argument count mismatches aren't caught at all when the callee is a generic function
11:15:52
scymtym
i think the problem is that SB-C:FIND-GLOBAL-FUN does not take :where-from :defined-method into account
13:06:08
scymtym
i tried (defun foo (x y) (class-name x y)) with sbcl-1.4.15 and it doesn't signal a warning
13:17:12
jdz
So yes, it would be nice if this warning would be emitted when the callee is a generic function without setting sb-ext:*derive-function-types*.
15:44:23
stassats
fine, but doing (defmethod whatever (x) (whatever x 32)) for the first time doesn't warn