I cant find: was or not that proposal...
But can we have Async Class with async constructor and async super?
//AsyncClass
async_class AsyncClass { // keyword async_class(example)
constructor() {
await something(); //now constructor async too
}}
//AsyncObj in some async method
let NewAsyncObj = a
"Is an async factory function/method not sufficient to do this?"
Maybe, but i think it question similiar to "factory vs class":
we can use Сlass now, but why not to extend it to Async then?
"Also, note that you can return promises out of the constructor (and I've
done it before)"
Like callback?
"It gets ugly(ier) when you want to extend that. :-) "
Ok, i get it, but yes i prefer some more sugar like as i suggested before.
___
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss
"You can just call an async method from the constructor (without await) -
and then let that async method handle all the asynchronicity."
Not sure about it - how control? callback?
I prefer async/await then.
"I think async constructor would make more sense than async class"
Maybe: i use it for c
"new MyObject() would return a promise "
I have one idea about it, but not sure good or not...
async class and then newAsync
Maybe this way more good for someone...
___
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es
"Long story short, introducing this feature would slow down new/
Reflect.construct"
"since this might suggest it returning a Promise, which it mustn't "
Can it help: if async class constructor will be return Promise(obj) and i
suggest before use newAsync for that practice?
Slow... but how much?
"I think awaitNew MyObject() would fit the thrust of your idea more"
For me more good my first version... async class = return Promise(obj)
But i can agree with others decisions, if in the end i get: easy way to
async new
Some people ask me for some more interesting sample...
Maybe it can help -
"why a static factory"
I answered earlier:
<>
Yes, you can, but for me more easy to work with classes.
And i just want to extend the functionality for work with async - that all.
___
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.or
"ES classes are about 90% sugar"
"ES classes aren't like traditional classes"
Yes and i just want to more sugar for them - just simple.
___
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss
"why a static factory"
And more notes:
"return img" - this is cut version
In my example you get obj - not image.
And my sample was simple.
I hope not so long left to class private var + decorators
And sample can be then more complex with it:
async class Class{
@some_decorator
static private met
```js
class Test{
constructor(){}
async init(){}
static async newA(){
let obj = new Test(); obj.init(); return obj
}}
let t = Test.newA();
class ExtTest extends Test(){
constructor(){
super(); // we cant init here
//now we must recreate new/init for ExtTest too
}}
```
Or with my proposal we can ea
([Classes][1]):
[1]:
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes
«JavaScript classes, introduced in ECMAScript 2015, are primarily
syntactical sugar over JavaScript's existing prototype-based inheritance.
The class syntax does not introduce a new object-oriented inheri
Class|PromiseClass
constructor(){ await super();} //async()=>Promise object
}//AsyncClass
```
[1]:https://repl.it/repls/InsubstantialPortlyCores
вс, 25 февр. 2018 г. в 11:47, Dimitrian Nine :
> ([Classes][1]):
> [1]:
> https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes
>
>Not a bad idea, but I'd strongly prefer the promise to be returned from
new >AsyncClass(...) itself instead
This about wrapper? He is just example of how functional can work right now.
>I do have a preference: async should decorate the constructor, not the
class
How i say before: both variants f
s
```
[1]: https://repl.it/repls/FinancialUnknownDehardwarization
вт, 27 авг. 2019 г. в 07:42, Dimitrian Nine :
> >Not a bad idea, but I'd strongly prefer the promise to be returned from
> new >AsyncClass(...) itself instead
> This about wrapper? He is just example of how functional can work ri
Claude Pache
> class consists not only of its constructor
How i see it - seems all think that my idea not bad, but we have semantic
hell.
My thougth was Class is wrapper for constructor object
And Async Class is same wrapper for constructor Promise of object
kai zhu
>class-factories are good enou
Maybe i don't know something, but want to proposal idea:
We have emojis and other symbols, that have many codepoints
And 'emoji'.length > 1
My idea that we have something like
'emoji'.symbols - and get array of symbols, where symbol is array of
codepoints
And maybe method SymbolAt
'emoji'.SymobolAt
Thanks i found same ideas here:
https://esdiscuss.org/topic/string-prototype-symbolat-improved-string-prototype-charat
https://esdiscuss.org/topic/working-with-grapheme-clusters
But topics was created - 6 years ago... And no news for working on it?
___
Update: [now we have proposal 1 stage][1]
[1]: https://github.com/bmeck/proposal-async-init/issues/1
___
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss
19 matches
Mail list logo