Improve TreeTypeAdapter thread-safety #1976
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Gson claims to be thread-safe so
TreeTypeAdapter.delegate()
might be called by multiple threads. To guarantee that each thread sees a fully constructeddelegate
, the field has to bevolatile
.Otherwise when a user-defined type adapter with non-
final
fields (even though it is stateless) is being used as delegate a thread might see an incomplete constructed instance. See Safe Publication and Safe Initialization in Java; the current case ofTreeTypeAdapter.delegate()
would be similar to the "Unsafe Local DCL & Unsafe Singleton" case shown in that blog post.