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

Double-Checked Locking #40

Closed
QiAnXinCodeSafe opened this issue Jan 14, 2020 · 0 comments
Closed

Double-Checked Locking #40

QiAnXinCodeSafe opened this issue Jan 14, 2020 · 0 comments

Comments

@QiAnXinCodeSafe
Copy link

QiAnXinCodeSafe commented Jan 14, 2020

if (singleton == null) {
synchronized (WordDictionary.class) {
if (singleton == null) {
singleton = new WordDictionary();
return singleton;

Double-Checked Locking is widely cited and used as an efficient method for implementing lazy initialization in a multithreaded environment.
Unfortunately, it will not work reliably in a platform independent way when implemented in Java, without additional synchronization.
declares the singleton field volatile offers a much more elegant solution

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

2 participants