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
Currently Rtc allows only the annotation of classes. It should also allow the annotation of modules. This will also let us do the following:
classIncluderClassinclude:module1,:module2,...
end
The includes will look up the modules, and for each module add the method annotations of that module to the current class (or theoretically, another module). Different handling for conflicting signatures will be required for this to work. That is, if module Foo defines a method bar with some signature sig1 and class A also defines bar with signature sig2, and A includes Foo, then the signatures sig1 and sig2 should not be automatically intersected, but rather the signature from A should overwrite the signature from Foo.
The text was updated successfully, but these errors were encountered:
self annotations on modules currently work. In addition it'd be nice if we could use modules as names in the grammar, so that a method would accept only objects whose class includes the some specified module (see the set class for a use case for this).
Currently Rtc allows only the annotation of classes. It should also allow the annotation of modules. This will also let us do the following:
The
includes
will look up the modules, and for each module add the method annotations of that module to the current class (or theoretically, another module). Different handling for conflicting signatures will be required for this to work. That is, if moduleFoo
defines a methodbar
with some signature sig1 and classA
also definesbar
with signature sig2, andA
includesFoo
, then the signatures sig1 and sig2 should not be automatically intersected, but rather the signature fromA
should overwrite the signature fromFoo
.The text was updated successfully, but these errors were encountered: