Александр Ефремов (2018-02-12T07:44:09.000Z)
mr.efrem at gmail.com (2018-02-12T07:59:57.875Z)
I just considered this proposal in a context of `node.js` environment. I write microservices which execute requests to database and other microservices. All such requests are asynchronous. Therefore I execute them in body of async function. And sometimes I forget to add `await` for such operations. I thought that possible to implement that only for `async await` and didn't know that it transpiling to promises queue. I right understand that general problem in that? But also is need sometimes don't wait ending of the call. For example if on the browser side we execute operation adding row to the any list and after that to get actual list rows we execute still one request to the backend then we can don't wait ending that query and return to the list rows page for example. I.e. in such cases result of that promise isn't important in context that function.
mr.efrem at gmail.com (2018-02-12T07:59:09.902Z)
I just considered this proposal in a context of `node.js` environment. I write microservices which execute requests to database and other microservices. All such requests are asynchronous. Therefore I execute them in body of async function. And sometimes I forget to add `await` for such operations. I thought that possible to implement that only for `async await` and didn't know that it transpiling to promises queue. I right understand that general problem in that? But also is need sometimes don't wait ending of the call. For example if on the browser side we execute operation adding row to the any list and after that to get actual list rows again from the backend we can don't wait ending that query and return to the list rows page for example. I.e. in such cases result of that promise isn't important in context that function.
mr.efrem at gmail.com (2018-02-12T07:58:51.093Z)
I just considered this proposal in a context of `node.js` environment. I write microservices which execute requests to database and other microservices. All such requests are asynchronous. Therefore I execute them in body of async function. And sometimes I forget to add `await` for such operations. I thought that possible to implement that only for `async await` and didn't know that it transpiling to promises queue. I right understand that general problem in that? But also is need sometimes don't wait ending of the call. For example if on the browser side we execute operation adding row to the any list and after that to get actual list rows again from the backend we can don't wait ending that query and return to the list rows page for example. I.e. in such cases result of that promise isn't important in context that function.