Does extension return new instance each time
Consider this case, a variable declared in an extension, like this.
extension UIViewController {
var apiClient: APIClient {
return APIClientImplementation()
}
}
Does this extension return a new instance each time i call it from a different UIViewController, if so how this affects the memory ?
If not could this cause a problem, that i am getting the same instance for all the UIViewController's that i am using this instance in, and as you can tell its an APIClient instance that is used to be injected into another instance of a GateWay class, can this lead to a problem in the future ?
Note:
GateWayclass is class instance that i am using to execute API requests, each chunk of services has its own gateway.
I know i can use protocol to apply rules on the desired UIViewController to create instance each time.
What i am trying to achieve is to write less code with less problems in the future, and remove unnecessary chunks of code.
swift memory foundation swift-extensions
asked Jan 20 at 9:41
Mohmmad SMohmmad S
1,6611418
add a comment |
Consider this case, a variable declared in an extension, like this.
extension UIViewController {
var apiClient: APIClient {
return APIClientImplementation()
}
}
Does this extension return a new instance each time i call it from a different UIViewController, if so how this affects the memory ?
If not could this cause a problem, that i am getting the same instance for all the UIViewController's that i am using this instance in, and as you can tell its an APIClient instance that is used to be injected into another instance of a GateWay class, can this lead to a problem in the future ?
Note:
GateWayclass is class instance that i am using to execute API requests, each chunk of services has its own gateway.
I know i can use protocol to apply rules on the desired UIViewController to create instance each time.
What i am trying to achieve is to write less code with less problems in the future, and remove unnecessary chunks of code.
swift memory foundation swift-extensions
asked Jan 20 at 9:41
Mohmmad SMohmmad S
1,6611418
Although I am unable the understand the question, but basicallyapiClientdoes returns a new instance each time... By default it should get deallocated when the view controller gets deallocated.
– Ahmad F
Jan 20 at 9:57
So no memory hustle at any point or crashes, since this instance could be taken to a background thread for work
– Mohmmad S
Jan 20 at 9:58
add a comment |
Consider this case, a variable declared in an extension, like this.
extension UIViewController {
var apiClient: APIClient {
return APIClientImplementation()
}
}
Does this extension return a new instance each time i call it from a different UIViewController, if so how this affects the memory ?
If not could this cause a problem, that i am getting the same instance for all the UIViewController's that i am using this instance in, and as you can tell its an APIClient instance that is used to be injected into another instance of a GateWay class, can this lead to a problem in the future ?
Note:
GateWayclass is class instance that i am using to execute API requests, each chunk of services has its own gateway.
I know i can use protocol to apply rules on the desired UIViewController to create instance each time.
What i am trying to achieve is to write less code with less problems in the future, and remove unnecessary chunks of code.
swift memory foundation swift-extensions
asked Jan 20 at 9:41
Mohmmad SMohmmad S
1,6611418
Consider this case, a variable declared in an extension, like this.
extension UIViewController {
var apiClient: APIClient {
return APIClientImplementation()
}
}
Does this extension return a new instance each time i call it from a different UIViewController, if so how this affects the memory ?
If not could this cause a problem, that i am getting the same instance for all the UIViewController's that i am using this instance in, and as you can tell its an APIClient instance that is used to be injected into another instance of a GateWay class, can this lead to a problem in the future ?
Note:
GateWayclass is class instance that i am using to execute API requests, each chunk of services has its own gateway.
I know i can use protocol to apply rules on the desired UIViewController to create instance each time.
What i am trying to achieve is to write less code with less problems in the future, and remove unnecessary chunks of code.
swift memory foundation swift-extensions
swift memory foundation swift-extensions
asked Jan 20 at 9:41
Mohmmad SMohmmad S
1,6611418
asked Jan 20 at 9:41
Mohmmad SMohmmad S
1,6611418
asked Jan 20 at 9:41
Mohmmad SMohmmad S
1,6611418
asked Jan 20 at 9:41
Mohmmad SMohmmad S
1,6611418
asked Jan 20 at 9:41
Mohmmad SMohmmad S
1,6611418
1,6611418
Although I am unable the understand the question, but basicallyapiClientdoes returns a new instance each time... By default it should get deallocated when the view controller gets deallocated.
– Ahmad F
Jan 20 at 9:57
So no memory hustle at any point or crashes, since this instance could be taken to a background thread for work
– Mohmmad S
Jan 20 at 9:58
add a comment |
Although I am unable the understand the question, but basicallyapiClientdoes returns a new instance each time... By default it should get deallocated when the view controller gets deallocated.
– Ahmad F
Jan 20 at 9:57
So no memory hustle at any point or crashes, since this instance could be taken to a background thread for work
– Mohmmad S
Jan 20 at 9:58
Although I am unable the understand the question, but basically
apiClient does returns a new instance each time... By default it should get deallocated when the view controller gets deallocated.– Ahmad F
Jan 20 at 9:57
Although I am unable the understand the question, but basically
apiClient does returns a new instance each time... By default it should get deallocated when the view controller gets deallocated.– Ahmad F
Jan 20 at 9:57
So no memory hustle at any point or crashes, since this instance could be taken to a background thread for work
– Mohmmad S
Jan 20 at 9:58
So no memory hustle at any point or crashes, since this instance could be taken to a background thread for work
– Mohmmad S
Jan 20 at 9:58
add a comment |
1 Answer
1
active
oldest
votes
Yes, everytime you access apiClient from any viewController, a new instance of APIClient will be returned.
As apiClient variable is get only so this itself can not cause any memory issues.
answered Jan 20 at 10:55
KamranKamran
6,72521028
so i can work with it in background threads with no problems what so ever ?
– Mohmmad S
Jan 20 at 10:56
As it looks this is not going to do anything with UI so yes, it should be able to work in background without any issue. But without understanding all the use cases, it's difficult to say it won't create any issue ever.
– Kamran
Jan 20 at 11:00
add a comment |
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%2f54275194%2fdoes-extension-return-new-instance-each-time%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Yes, everytime you access apiClient from any viewController, a new instance of APIClient will be returned.
As apiClient variable is get only so this itself can not cause any memory issues.
answered Jan 20 at 10:55
KamranKamran
6,72521028
so i can work with it in background threads with no problems what so ever ?
– Mohmmad S
Jan 20 at 10:56
As it looks this is not going to do anything with UI so yes, it should be able to work in background without any issue. But without understanding all the use cases, it's difficult to say it won't create any issue ever.
– Kamran
Jan 20 at 11:00
add a comment |
Yes, everytime you access apiClient from any viewController, a new instance of APIClient will be returned.
As apiClient variable is get only so this itself can not cause any memory issues.
answered Jan 20 at 10:55
KamranKamran
6,72521028
so i can work with it in background threads with no problems what so ever ?
– Mohmmad S
Jan 20 at 10:56
As it looks this is not going to do anything with UI so yes, it should be able to work in background without any issue. But without understanding all the use cases, it's difficult to say it won't create any issue ever.
– Kamran
Jan 20 at 11:00
add a comment |
Yes, everytime you access apiClient from any viewController, a new instance of APIClient will be returned.
As apiClient variable is get only so this itself can not cause any memory issues.
answered Jan 20 at 10:55
KamranKamran
6,72521028
Yes, everytime you access apiClient from any viewController, a new instance of APIClient will be returned.
As apiClient variable is get only so this itself can not cause any memory issues.
answered Jan 20 at 10:55
KamranKamran
6,72521028
answered Jan 20 at 10:55
KamranKamran
6,72521028
answered Jan 20 at 10:55
KamranKamran
6,72521028
answered Jan 20 at 10:55
KamranKamran
6,72521028
6,72521028
so i can work with it in background threads with no problems what so ever ?
– Mohmmad S
Jan 20 at 10:56
As it looks this is not going to do anything with UI so yes, it should be able to work in background without any issue. But without understanding all the use cases, it's difficult to say it won't create any issue ever.
– Kamran
Jan 20 at 11:00
add a comment |
so i can work with it in background threads with no problems what so ever ?
– Mohmmad S
Jan 20 at 10:56
As it looks this is not going to do anything with UI so yes, it should be able to work in background without any issue. But without understanding all the use cases, it's difficult to say it won't create any issue ever.
– Kamran
Jan 20 at 11:00
so i can work with it in background threads with no problems what so ever ?
– Mohmmad S
Jan 20 at 10:56
so i can work with it in background threads with no problems what so ever ?
– Mohmmad S
Jan 20 at 10:56
As it looks this is not going to do anything with UI so yes, it should be able to work in background without any issue. But without understanding all the use cases, it's difficult to say it won't create any issue ever.
– Kamran
Jan 20 at 11:00
As it looks this is not going to do anything with UI so yes, it should be able to work in background without any issue. But without understanding all the use cases, it's difficult to say it won't create any issue ever.
– Kamran
Jan 20 at 11:00
add a comment |
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%2f54275194%2fdoes-extension-return-new-instance-each-time%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
Although I am unable the understand the question, but basically
apiClientdoes returns a new instance each time... By default it should get deallocated when the view controller gets deallocated.– Ahmad F
Jan 20 at 9:57
So no memory hustle at any point or crashes, since this instance could be taken to a background thread for work
– Mohmmad S
Jan 20 at 9:58