Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Selector aliasing: Renamings of message sends #16

Open
PragTob opened this issue Jan 12, 2013 · 0 comments
Open

Selector aliasing: Renamings of message sends #16

PragTob opened this issue Jan 12, 2013 · 0 comments

Comments

@PragTob
Copy link
Collaborator

PragTob commented Jan 12, 2013

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant