Mixing
What is the syntax for Function.prototype.call or Function.prototype.apply with an async function
-1
What is the syntax for using the call() or apply() methods to change this when dealing async functions?
So by way of example:
class Foo {
async someLongMethod(){
... Do stuff
}
}
class Bar {
async someOtherMethodThatWillWait(){
//Will the following work?
await Foo.prototype.someLongMethod.call(this);
}
}
javascript async-await
asked Nov 22 '18 at 8:14
Tom MaherTom Maher
7541230
|
show 2 more comments
-1
What is the syntax for using the call() or apply() methods to change this when dealing async functions?
So by way of example:
class Foo {
async someLongMethod(){
... Do stuff
}
}
class Bar {
async someOtherMethodThatWillWait(){
//Will the following work?
await Foo.prototype.someLongMethod.call(this);
}
}
javascript async-await
asked Nov 22 '18 at 8:14
Tom MaherTom Maher
7541230
2
Will the following workWhy not just try it? It looks OK to me
– CertainPerformance
Nov 22 '18 at 8:15
1
awaitacts on promises, so as that method returns a promise you're fine. It's certainly syntactically valid.
– jonrsharpe
Nov 22 '18 at 8:16
@jonrsharpe Since it's anasyncfunction, it will necessarily return aPromise
– CertainPerformance
Nov 22 '18 at 8:16
@CertainPerformance ah, hadn't spotted that it was also in the example, thanks!
– jonrsharpe
Nov 22 '18 at 8:17
1
No, Promises in any form are not synchronous (except when calling the constructor, initially)
– CertainPerformance
Nov 22 '18 at 8:33
|
show 2 more comments
-1
-1
-1
What is the syntax for using the call() or apply() methods to change this when dealing async functions?
So by way of example:
class Foo {
async someLongMethod(){
... Do stuff
}
}
class Bar {
async someOtherMethodThatWillWait(){
//Will the following work?
await Foo.prototype.someLongMethod.call(this);
}
}
javascript async-await
asked Nov 22 '18 at 8:14
Tom MaherTom Maher
7541230
What is the syntax for using the call() or apply() methods to change this when dealing async functions?
So by way of example:
class Foo {
async someLongMethod(){
... Do stuff
}
}
class Bar {
async someOtherMethodThatWillWait(){
//Will the following work?
await Foo.prototype.someLongMethod.call(this);
}
}
javascript async-await
javascript async-await
asked Nov 22 '18 at 8:14
Tom MaherTom Maher
7541230
asked Nov 22 '18 at 8:14
Tom MaherTom Maher
7541230
asked Nov 22 '18 at 8:14
Tom MaherTom Maher
7541230
asked Nov 22 '18 at 8:14
Tom MaherTom Maher
7541230
asked Nov 22 '18 at 8:14
Tom MaherTom Maher
7541230
7541230
2
Will the following workWhy not just try it? It looks OK to me
– CertainPerformance
Nov 22 '18 at 8:15
1
awaitacts on promises, so as that method returns a promise you're fine. It's certainly syntactically valid.
– jonrsharpe
Nov 22 '18 at 8:16
@jonrsharpe Since it's anasyncfunction, it will necessarily return aPromise
– CertainPerformance
Nov 22 '18 at 8:16
@CertainPerformance ah, hadn't spotted that it was also in the example, thanks!
– jonrsharpe
Nov 22 '18 at 8:17
1
No, Promises in any form are not synchronous (except when calling the constructor, initially)
– CertainPerformance
Nov 22 '18 at 8:33
|
show 2 more comments
2
Will the following workWhy not just try it? It looks OK to me
– CertainPerformance
Nov 22 '18 at 8:15
1
awaitacts on promises, so as that method returns a promise you're fine. It's certainly syntactically valid.
– jonrsharpe
Nov 22 '18 at 8:16
@jonrsharpe Since it's anasyncfunction, it will necessarily return aPromise
– CertainPerformance
Nov 22 '18 at 8:16
@CertainPerformance ah, hadn't spotted that it was also in the example, thanks!
– jonrsharpe
Nov 22 '18 at 8:17
1
No, Promises in any form are not synchronous (except when calling the constructor, initially)
– CertainPerformance
Nov 22 '18 at 8:33
2
2
Will the following work Why not just try it? It looks OK to me– CertainPerformance
Nov 22 '18 at 8:15
Will the following work Why not just try it? It looks OK to me– CertainPerformance
Nov 22 '18 at 8:15
1
1
await acts on promises, so as that method returns a promise you're fine. It's certainly syntactically valid.– jonrsharpe
Nov 22 '18 at 8:16
await acts on promises, so as that method returns a promise you're fine. It's certainly syntactically valid.– jonrsharpe
Nov 22 '18 at 8:16
@jonrsharpe Since it's an
async function, it will necessarily return a Promise– CertainPerformance
Nov 22 '18 at 8:16
@jonrsharpe Since it's an
async function, it will necessarily return a Promise– CertainPerformance
Nov 22 '18 at 8:16
@CertainPerformance ah, hadn't spotted that it was also in the example, thanks!
– jonrsharpe
Nov 22 '18 at 8:17
@CertainPerformance ah, hadn't spotted that it was also in the example, thanks!
– jonrsharpe
Nov 22 '18 at 8:17
1
1
No, Promises in any form are not synchronous (except when calling the constructor, initially)
– CertainPerformance
Nov 22 '18 at 8:33
No, Promises in any form are not synchronous (except when calling the constructor, initially)
– CertainPerformance
Nov 22 '18 at 8:33
|
show 2 more comments
1 Answer
1
active
oldest
votes
2
It's exactly the same as the syntax for calling normal functions, there is no difference. You cannot really distinguish an async function from any other function that returns a promise.
answered Nov 22 '18 at 9:07
BergiBergi
373k59562893
I managed to test the call within protractor through node using a browser wait and it does indeed work. Thanks for everyone's input.
– Tom Maher
Nov 22 '18 at 10:09
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
});
}
});
draft saved
draft discarded
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%2f53426463%2fwhat-is-the-syntax-for-function-prototype-call-or-function-prototype-apply-with%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
2
It's exactly the same as the syntax for calling normal functions, there is no difference. You cannot really distinguish an async function from any other function that returns a promise.
answered Nov 22 '18 at 9:07
BergiBergi
373k59562893
I managed to test the call within protractor through node using a browser wait and it does indeed work. Thanks for everyone's input.
– Tom Maher
Nov 22 '18 at 10:09
add a comment |
2
It's exactly the same as the syntax for calling normal functions, there is no difference. You cannot really distinguish an async function from any other function that returns a promise.
answered Nov 22 '18 at 9:07
BergiBergi
373k59562893
I managed to test the call within protractor through node using a browser wait and it does indeed work. Thanks for everyone's input.
– Tom Maher
Nov 22 '18 at 10:09
add a comment |
2
2
2
It's exactly the same as the syntax for calling normal functions, there is no difference. You cannot really distinguish an async function from any other function that returns a promise.
answered Nov 22 '18 at 9:07
BergiBergi
373k59562893
It's exactly the same as the syntax for calling normal functions, there is no difference. You cannot really distinguish an async function from any other function that returns a promise.
answered Nov 22 '18 at 9:07
BergiBergi
373k59562893
answered Nov 22 '18 at 9:07
BergiBergi
373k59562893
answered Nov 22 '18 at 9:07
BergiBergi
373k59562893
answered Nov 22 '18 at 9:07
BergiBergi
373k59562893
373k59562893
I managed to test the call within protractor through node using a browser wait and it does indeed work. Thanks for everyone's input.
– Tom Maher
Nov 22 '18 at 10:09
add a comment |
I managed to test the call within protractor through node using a browser wait and it does indeed work. Thanks for everyone's input.
– Tom Maher
Nov 22 '18 at 10:09
I managed to test the call within protractor through node using a browser wait and it does indeed work. Thanks for everyone's input.
– Tom Maher
Nov 22 '18 at 10:09
I managed to test the call within protractor through node using a browser wait and it does indeed work. Thanks for everyone's input.
– Tom Maher
Nov 22 '18 at 10:09
add a comment |
draft saved
draft discarded
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.
draft saved
draft discarded
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%2f53426463%2fwhat-is-the-syntax-for-function-prototype-call-or-function-prototype-apply-with%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
2
Will the following workWhy not just try it? It looks OK to me– CertainPerformance
Nov 22 '18 at 8:15
1
awaitacts on promises, so as that method returns a promise you're fine. It's certainly syntactically valid.– jonrsharpe
Nov 22 '18 at 8:16
@jonrsharpe Since it's an
asyncfunction, it will necessarily return aPromise– CertainPerformance
Nov 22 '18 at 8:16
@CertainPerformance ah, hadn't spotted that it was also in the example, thanks!
– jonrsharpe
Nov 22 '18 at 8:17
1
No, Promises in any form are not synchronous (except when calling the constructor, initially)
– CertainPerformance
Nov 22 '18 at 8:33