Search
8:12:14
Krystof
so, why did we take out the defmethod-with-no-defgeneric warning anyway?
8:12:58
Krystof
it operated at load-time, which was probably the wrong time. What if we wrote a compile-time equivalent?
8:27:38
flip214
hmmm, how did I get this? ; caught WARNING: The function NIL is called with odd number of keyword arguments.
8:28:45
flip214
ah, a symbol from another package that wasn't exported, and I clicked the compiler error away ;)
8:54:08
Shinmera
Krystof: if I remember correctly stassats was annoyed by it and took it out
16:02:00
phoe
https://plaster.tymoon.eu/view/2160#2160
16:02:24
phoe
This last SETF should be a no-op, but instead it causes a compile-time warning
16:03:18
phoe
am I being dumb with this code somewhere, or is the issue elsewhere?
16:04:23
_death
are you talking about PARENT not used warning?
16:04:54
phoe
_death: I've edited the paste
16:05:06
mfiano
Derived type of PARENT is (VALUES (OR ENTITY NULL) &OPTIONAL),conflicting with its asserted type COMMON-LISP-USER::NODE.
16:06:45
_death
that makes sense to me, since NODE-CHILDREN expects a NODE, which PARENT isn't
16:07:55
phoe
yes - me and mfiano are dumb
16:08:05
phoe
the type of PARENT should be NODE, not ENTITY
16:08:14
mfiano
What else is new (for me anyway)? :)