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
Case 1: Rename methods of traits (e.g. on conflicts):
explicit renamings (#select → #oldSelect), but trait code might use the original message names idea: => Tool support, since it's hard to detect all calls in a dynamically typed language: present candidates to the programmer (exception: self select etc.)
Case 2: Incomplete classes
"traits" that require certain messages in the target
example: trait T requires a method XY that does Z, class C provides AB that does Z: programmers explicitly specify that AB in C is XY and tool support that renames message sends in trait code
More concrete example: Colelction methods like select require a working implementation of do which might in turn be named each cause a stupid ruby programmer wrote it.
The text was updated successfully, but these errors were encountered:
Case 1: Rename methods of traits (e.g. on conflicts):
explicit renamings (#select → #oldSelect), but trait code might use the original message names
idea: => Tool support, since it's hard to detect all calls in a dynamically typed language: present candidates to the programmer (exception: self select etc.)
Case 2: Incomplete classes
"traits" that require certain messages in the target
More concrete example: Colelction methods like
select
require a working implementation ofdo
which might in turn be namedeach
cause a stupid ruby programmer wrote it.The text was updated successfully, but these errors were encountered: