You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
open generic-function \= (<date>, <date>) => (<boolean>);
The failure says:
date-protocol-functions-test failed
function = argument 0 type {class <object>} is a supertype of the specified
type {class <date>} failed [expression "subtype?(actual, spec)" evaluates
to #f, not a true value.]
(The sense of sub/super-type in the error is incorrect but that's not the issue here.)
This is checking the wrong thing. What this spec wants to check is that there is a specific method on = for (<date>, <date>) but what it's actually checking is that the = gf exists and is defined on parameters that are subtypes of <date>.
In #112 I remove generic-function specs because generic function does exactly the same thing. That works for define function, define generic, and for implicit generic functions defined by define method (not that that's much use).
I think the spec for checking that a particular method exists should just be called method, assuming that doesn't cause any parsing problems.
In the System test suite the spec says:
The failure says:
(The sense of sub/super-type in the error is incorrect but that's not the issue here.)
This is checking the wrong thing. What this spec wants to check is that there is a specific method on
=
for(<date>, <date>)
but what it's actually checking is that the=
gf exists and is defined on parameters that are subtypes of<date>
.I propose a new spec:
to do the needful here.
The text was updated successfully, but these errors were encountered: