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
It seems that some projects (see #164 and eclipse/eclipse-collections#128) use template files to generate abstract skeletal implementers for a particular interface. This seems to be particularly useful for generating skeletal implementation classes that deal with all the primitive types.
Currently, the tool does not analyze or manipulate such template files. It would be particularly useful to identify source code files generated from templates and, instead of manipulating the derived source code, manipulating the corresponding template mechanism.
The text was updated successfully, but these errors were encountered:
These implementations were automatically copied to PrimitiveIterable. This step represents the corresponding removable. This is a manual step and a workaround of ponder-lab/Migrate-Skeletal-Implementation-to-Interface-Refactoring#165.
Signed-off-by: Raffi Khatchadourian <rkhatchadourian@citytech.cuny.edu>
itohro
pushed a commit
to eclipse/eclipse-collections
that referenced
this issue
Jul 13, 2016
…oring.
* Applied skeletal implementation to interface migration automated refactoring.
Signed-off-by: Raffi Khatchadourian <rkhatchadourian@citytech.cuny.edu>
* Unmigrate methods that crossed module boundaries.
Signed-off-by: Raffi Khatchadourian <rkhatchadourian@citytech.cuny.edu>
* Convert tab characters to spaces.
Signed-off-by: Raffi Khatchadourian <rkhatchadourian@citytech.cuny.edu>
* Remove unused import straggler.
Signed-off-by: Raffi Khatchadourian <rkhatchadourian@citytech.cuny.edu>
* Move curly brace to newline to conform to destination interface coding styles.
There are differences in coding styles between the source module, where the implementations originated, and the destination module, where the default methods were created. This commit is to conform to to new coding style. This is a manual step as we do not currently analyze the difference in coding styles between projects/modules.
Signed-off-by: Raffi Khatchadourian <rkhatchadourian@citytech.cuny.edu>
* Removed skeletal implementations from template file.
These implementations were automatically copied to PrimitiveIterable. This step represents the corresponding removable. This is a manual step and a workaround of ponder-lab/Migrate-Skeletal-Implementation-to-Interface-Refactoring#165.
Signed-off-by: Raffi Khatchadourian <rkhatchadourian@citytech.cuny.edu>
It seems that some projects (see #164 and eclipse/eclipse-collections#128) use template files to generate abstract skeletal implementers for a particular interface. This seems to be particularly useful for generating skeletal implementation classes that deal with all the primitive types.
Currently, the tool does not analyze or manipulate such template files. It would be particularly useful to identify source code files generated from templates and, instead of manipulating the derived source code, manipulating the corresponding template mechanism.
The text was updated successfully, but these errors were encountered: