commit | cd864dc7b2e50bda38a52946c4759245697b306d | [log] [tgz] |
---|---|---|
author | Fabrice Tiercelin <fabrice.tiercelin@yahoo.fr> | Tue May 04 19:55:40 2021 +0200 |
committer | Fabrice Tiercelin <fabrice.tiercelin@yahoo.fr> | Sat May 15 09:15:55 2021 -0400 |
tree | 6688b65f7c1fcc1bb699e6e889c71f2f8dfa10a9 | |
parent | 24aca42ef166d343db0203d349cf56f46c79611a [diff] |
Bug 573358 - [AutoRefactor #83/153] Pull out if from an if/else Moves an inner if condition around the outer if condition: - The inner if condition should be common to both if/else clauses of the outer if statement, - The if conditions should be passive. Given: if (b1) { if (b2) { System.out.println("foo"); } } else { if (b2) { System.out.println("bar"); } } When: Applying "Pull out a duplicate 'if' from an if/else" clean up... Then: if (b2) { if (b1) { System.out.println("foo"); } else { System.out.println("bar"); } } Change-Id: I2908d6433760691b61d227804c7854044c4851c2 Signed-off-by: Fabrice Tiercelin <fabrice.tiercelin@yahoo.fr> Reviewed-on: https://git.eclipse.org/r/c/jdt/eclipse.jdt.ui/+/180171 Reviewed-by: Carsten Hammer <carsten.hammer@t-online.de> Tested-by: JDT Bot <jdt-bot@eclipse.org>
Thanks for your interest in this project.
The JDT UI implements the user interface for the Java IDE. This includes views like Package Explorer and JUnit, the Java and properties files editors, Java search, and refactorings. Website: http://www.eclipse.org/jdt/ui/
Contributions to JDT UI are most welcome. There are many ways to contribute, from entering high quality bug reports, to contributing code or documentation changes. For a complete guide, see the [How to Contribute] 1 page on the team wiki.
Information regarding source code management, builds, coding standards, and more.
Before your contribution can be accepted by the project, you need to create and electronically sign the Eclipse Foundation Contributor License Agreement (CLA).
Public forum for Eclipse JDT users.
This project uses Bugzilla to track ongoing development and issues.
Be sure to search for existing bugs before you create another one. Remember that contributions are always welcome!
Contact the project developers via the project's “dev” list.