Skip to content

Conversation

@ejona86
Copy link
Member

@ejona86 ejona86 commented Jan 9, 2025

We should avoid jsr305 and error prone's has the same semantics.

Fixes #8687


I'm aware there's plenty of other similar annotations. I'm taking them one-at-a-time because error prone's don't always have the same semantics and if we need to revert the changes for one annotation and I don't want to revert it for all of them.

I'm not planning to fully-remove jsr305 at the moment, just get things in a better state. This was prompted by seeing a glimpse of hope (google/guava#7571). I don't know why we didn't migrate this annotation earlier, though, other than it didn't get us anything directly.

We should avoid jsr305 and error prone's has the same semantics.

Fixes grpc#8687
@ejona86 ejona86 requested a review from larry-safran January 9, 2025 20:51
@ejona86
Copy link
Member Author

ejona86 commented Jan 9, 2025

CC @kluever (I also plan to send out GuardedBy soon.)

@kluever
Copy link
Contributor

kluever commented Jan 9, 2025

Awesome! @graememorgan is currently working on this inside of google3 as well.

@ejona86 ejona86 merged commit 7b5d069 into grpc:master Jan 9, 2025
16 checks passed
@ejona86 ejona86 deleted the jsr305-checkreturnvalue branch January 9, 2025 21:45
@ejona86 ejona86 mentioned this pull request Feb 4, 2025
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 10, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Migrate from JSR305's javax.annotation.CheckReturnValue to ErrorProne's com.google.errorprone.annotations.CheckReturnValue

3 participants