As a syntactic convenience, if all formals of the sender are passed through as arguments to the resend unchanged, then the simple resend keyword without an argument list is sufficient. The restrictions on the name, on the number of arguments, and on passing specialized objects through unchanged ensures that the methods considered as candidates are applicable to the name and arguments of the send. Resends may also be used to explicitly resolve ambiguities in the method lookup by filtering out undesired methods. This model of undirected and directed resends is a simplification of the Self rules, extended to the multiple dispatching case. Self's rules additionally support prioritized multiple inheritance and dynamic inheritance, neither of which is present in Cecil.
Self also allows the name and number of arguments to be changed as part of the resend.
In some cases, it appears to be useful to be able to change the name of the message as part of the resend. We are investigating possible semantics for resends where the name of the message is changed, so that both ambiguously-inherited methods can be invoked.