Skip to content

Use enhanced switch expressions where feasible #28014

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

Closed

Conversation

slutmaker
Copy link
Contributor

No description provided.

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged or decided on label Feb 7, 2022
@sbrannen sbrannen self-requested a review February 8, 2022 15:53
@sbrannen sbrannen self-assigned this Feb 8, 2022
@sbrannen sbrannen added type: task A general task and removed status: waiting-for-triage An issue we've not yet triaged or decided on labels Feb 8, 2022
@sbrannen sbrannen added this to the 6.0.0-M3 milestone Feb 8, 2022
@sbrannen sbrannen changed the title use enhanced switch expression Use enhanced switch expressions where feasible Feb 8, 2022
@sbrannen
Copy link
Member

sbrannen commented Feb 8, 2022

Please note that this PR currently fails the build.

Please address any issues (using ./gradlew build to verify build completes) and push changes to this PR.

@sbrannen sbrannen marked this pull request as draft February 8, 2022 15:56
@sbrannen sbrannen added the status: waiting-for-feedback We need additional information before we can continue label Feb 8, 2022
case WILDCARD_BOUND -> result.append('*');
case TYPE_ARGUMENT -> result.append(getStepArgument(i)).append(';');
default -> throw new AssertionError();
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please refrain from modifying classes under org.springframework.asm, org.springframework.cglib, and org.springframework.objenesis. Those include repackaged forks of the third-party libraries ASM, CGLIB, and Objenesis. Any refactoring to those classes should take place upstream in the originating repository. The Spring Framework will then pick up the changes when syncing with official updates of the forked third-party libraries.


Don't worry about it for this PR though. I'll revert those changes when merging.

@sbrannen sbrannen marked this pull request as ready for review February 18, 2022 15:45
sbrannen added a commit to sbrannen/spring-framework that referenced this pull request Feb 19, 2022
@sbrannen sbrannen closed this in c5c9267 Feb 19, 2022
@sbrannen sbrannen removed the status: waiting-for-feedback We need additional information before we can continue label Feb 19, 2022
@sbrannen
Copy link
Member

This has been merged into main in c5c9267 and revised in 8c6d59a.

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: task A general task
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants