As the question stated. Will I be allowed to do this:
class MyClass {
async constructor(){
return new Promise()
}
}
4 Answers
To expand upon what Patrick Roberts said, you cannot do what you are asking, but you can do something like this instead:
class MyClass {
constructor() {
//static initialization
}
async initialize() {
await WhatEverYouWant();
}
static async create() {
const o = new MyClass();
await o.initialize();
return o;
}
}
Then in your code create your object like this:
const obj = await MyClass.create();
1 Comment
rinogo
Thanks for answering the spirit of the question instead of just saying, "No, it's not allowed."
Without trying to fortune-tell about future decisions, let's concentrate on practicality and what is already known.
ES7, like ES6 before it will try to be a backwards compatible expansion to the language. With that in mind, a backwards compatible constructor function is essentially a regular function (with some runtime restrictions) that's meant to be invoked with the new keyword. When that happens, the function's return value gets special treatment, specifically, non-object return values are ignored and the newly allocated object is returned while object return values are returned as is (and the newly allocated object is thrown away). With that, your code would result in a promise being returned and no "object construction" would take place. I don't see the practicality of this and I suppose if anybody takes the time to find what to do with such code it will be rejected.
5 Comments
wintercounter
Makes sense. It isn't clear in the proposal. I was wondering it because you can still use a return value in the constructor so you won't receive your instance.
Amit
I didn't really get the chance to go through the proposal hence my hypothetical answer, but I'm fairly confident this will be defined as static code error.
Matt Molnar
If they were to add it, I think they would also have to add some way of defining an async class so that you would know to await the constructor function (which sounds tacky) in order to get around the issue that Amit presents.
Amit
@AnubhavSaini - I meant the object is not referenced by any variable, is inaccessible, and is later garbage collected. The language spec is publicly available.
You can get a promise from the return value, and await on that:
class User {
constructor() {
this.promise = this._init()
}
async _init() {
const response = await fetch('https://jsonplaceholder.typicode.com/users')
const users = await response.json()
this.user = users[Math.floor(Math.random() * users.length)]
}
}
(async () {
const user = new User()
await user.promise
return user
})().then(u => {
$('#result').text(JSON.stringify(u.user, null, 2))
}).catch(err => {
console.error(err)
})<script src="https://ajax.googleapis.com/ajax/libs/jquery/2.1.1/jquery.min.js"></script>
<pre id="result"><code></code></pre>
static asyncfunction that does the asynchronous initialization prior to actually constructing the instance ofMyClass.