Lazy property is initialized twice
As we all know lazy property is not thread safe.
my evaluation part is like this.
if someclass isInitialized {
return someclass instance
}
else{
initialize someclass
return someclass instance
}
The problem is
If thread 1 sees that someclass is not initialised it will then try to do so.
If thread 2 sees that someclass is not initialised before thread 1 gets to do so, then it too will try to initialise it too.
so it is initialized twice
can we overcome this with lazy property?
swift lazy-evaluation lazy-initialization
add a comment |
As we all know lazy property is not thread safe.
my evaluation part is like this.
if someclass isInitialized {
return someclass instance
}
else{
initialize someclass
return someclass instance
}
The problem is
If thread 1 sees that someclass is not initialised it will then try to do so.
If thread 2 sees that someclass is not initialised before thread 1 gets to do so, then it too will try to initialise it too.
so it is initialized twice
can we overcome this with lazy property?
swift lazy-evaluation lazy-initialization
Have a look at stackoverflow.com/questions/24024549/… and developer.apple.com/documentation/swift/cocoa_design_patterns/…, it shows how to use static properties to (lazily) instantiate shared instances (or other resources) in a thread-safe way.
– Martin R
Nov 21 '18 at 7:39
add a comment |
As we all know lazy property is not thread safe.
my evaluation part is like this.
if someclass isInitialized {
return someclass instance
}
else{
initialize someclass
return someclass instance
}
The problem is
If thread 1 sees that someclass is not initialised it will then try to do so.
If thread 2 sees that someclass is not initialised before thread 1 gets to do so, then it too will try to initialise it too.
so it is initialized twice
can we overcome this with lazy property?
swift lazy-evaluation lazy-initialization
As we all know lazy property is not thread safe.
my evaluation part is like this.
if someclass isInitialized {
return someclass instance
}
else{
initialize someclass
return someclass instance
}
The problem is
If thread 1 sees that someclass is not initialised it will then try to do so.
If thread 2 sees that someclass is not initialised before thread 1 gets to do so, then it too will try to initialise it too.
so it is initialized twice
can we overcome this with lazy property?
swift lazy-evaluation lazy-initialization
swift lazy-evaluation lazy-initialization
asked Nov 21 '18 at 7:35
Naveen PaulsinghNaveen Paulsingh
447
447
Have a look at stackoverflow.com/questions/24024549/… and developer.apple.com/documentation/swift/cocoa_design_patterns/…, it shows how to use static properties to (lazily) instantiate shared instances (or other resources) in a thread-safe way.
– Martin R
Nov 21 '18 at 7:39
add a comment |
Have a look at stackoverflow.com/questions/24024549/… and developer.apple.com/documentation/swift/cocoa_design_patterns/…, it shows how to use static properties to (lazily) instantiate shared instances (or other resources) in a thread-safe way.
– Martin R
Nov 21 '18 at 7:39
Have a look at stackoverflow.com/questions/24024549/… and developer.apple.com/documentation/swift/cocoa_design_patterns/…, it shows how to use static properties to (lazily) instantiate shared instances (or other resources) in a thread-safe way.
– Martin R
Nov 21 '18 at 7:39
Have a look at stackoverflow.com/questions/24024549/… and developer.apple.com/documentation/swift/cocoa_design_patterns/…, it shows how to use static properties to (lazily) instantiate shared instances (or other resources) in a thread-safe way.
– Martin R
Nov 21 '18 at 7:39
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53407227%2flazy-property-is-initialized-twice%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53407227%2flazy-property-is-initialized-twice%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Have a look at stackoverflow.com/questions/24024549/… and developer.apple.com/documentation/swift/cocoa_design_patterns/…, it shows how to use static properties to (lazily) instantiate shared instances (or other resources) in a thread-safe way.
– Martin R
Nov 21 '18 at 7:39