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

fix(pacmak): _ is not treated as a keyword in Java #4094

Merged
merged 7 commits into from
May 16, 2023

Conversation

rix0rrr
Copy link
Contributor

@rix0rrr rix0rrr commented May 12, 2023

Since Java 9, _ is considered a keyword. Although we are technically
still targeting Java 8 with our source, if we want our source to
be parseable by more modern tools or are considering raising the
threshold at some point, it would be good to have this in place already.

This might technically be considered breaking in case someone is
using _ as an identifier in a public API, since in newer releases
it will be renamed. But given that most jsii library authors will be
targeting users that will be running on recent Java versions, and Java 9
is ~6 years old, the chance of that happening in practice is vanishingly
small.


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Since Java 9, `_` is considered a keyword. Although we are technically
still targeting Java 8 with our source, if we want our source to
be parseable by more modern tools or are considering raising the
threshold at some point, it would be good to have this in place already.

This might technically be considered breaking in case someone is
using `_` as an identifier in a public API, since in newer releases
it will be renamed. But  given that most jsii library authors will be
targeting users that will be running on recent Java versions, and Java 9
is ~6 years old, the chance of that happening in practice is vanishingly
small.
@rix0rrr rix0rrr requested a review from a team May 12, 2023 12:28
@mergify mergify bot added the contribution/core This is a PR that came from AWS. label May 12, 2023
@mergify
Copy link
Contributor

mergify bot commented May 16, 2023

Thank you for contributing! ❤️ I will now look into making sure the PR is up-to-date, then proceed to try and merge it!

@mergify mergify bot added the pr/ready-to-merge This PR is ready to be merged. label May 16, 2023
@mergify
Copy link
Contributor

mergify bot commented May 16, 2023

Merging (with squash)...

@mergify mergify bot merged commit eaaf3ee into main May 16, 2023
29 checks passed
@mergify mergify bot deleted the huijbers/underscore-keyword branch May 16, 2023 12:51
@mergify mergify bot removed the pr/ready-to-merge This PR is ready to be merged. label May 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
contribution/core This is a PR that came from AWS.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants