freenode/#abcl - IRC Chatlog
Search
17:57:06
easye
Hmm. If your put the non-congruent method signatures from <https://plaster.tymoon.eu/view/2247#2247> into a file, it compiles ok.
18:03:49
easye
Filed <https://abcl.org/trac/ticket/485> for the problems with cl:eval of non-congruent generic method signatures
18:04:02
jackdaniel
easye: the congruency between the gf and the method is defined (among other rules), that method must have all key arguments from the generic function
18:04:45
jackdaniel
when you implicitly define the generic function via defmethod, and defmethod has &key arguments, the generic function is defined as (defgeneric foo (a &key)) [i.e for (defmethod foo ((a integer) &key z d))
18:09:45
easye
Alright. That's right: one doesn't typically use keyword arguments with generic functions for this reason.
21:44:50
alandipert
i'd be curious to hear if/how people are managing their ABCL(-contrib) dependencies on a per-project basis, if at all
21:45:41
alandipert
as opposed to dependencies on other asdf systems/jars. there seems to be something of a bootstrap problem with respect to the versioning of asdf itself. i can see how a Dockerfile is one way out
23:56:06
robertm
Is there any policy (or documentation) about when it is (or isn't) OK to load code that was compiled by ABCL version X into ABCL version Y?