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

Ensure proper null (as empty) handling for AtomicReference wrt serialization inclusion #740

Closed
cowtowncoder opened this issue Mar 30, 2015 · 1 comment
Milestone

Comments

@cowtowncoder
Copy link
Member

As per proposal on dev mailing list, I think it makes sense to make all referential types, like:

  • AtomicReference
  • JDK Optional
  • Guava Optional

work so that "absent" case (where non-null reference value refers to null or "absent") will match "empty" and "default" inclusion criteria, but NOT "null", for purposes of serialization filtering.

@cowtowncoder cowtowncoder added this to the 2.6.0 milestone Apr 29, 2015
@cowtowncoder
Copy link
Member Author

I believe this is now implemented.

cowtowncoder added a commit that referenced this issue Apr 29, 2015
@cowtowncoder cowtowncoder changed the title Ensure proper null (as empty) handling for AtomicReference Ensure proper null (as empty) handling for AtomicReference wrt serialization inclusion Sep 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant