Closed cprecioso closed 8 years ago
I don't want to introduce any transpilation or tool dependencies unless there is a really good reason to do so. Same thing with promises, I really can't see what we gain from such a change when one can simply wrap the existing API in promises and achieve the exact same effect.
No further response, closing.
I've been thinking of adapting the API to return
Promise
s in a backwards-compatible manner (check if the callback argument was used and if not, return aPromise
), and use them internally. Would this change be accepted?Also, if that is OK, even
async/await
functions from ES.next could be used internally in order to dramatically simplify almost all the code in the library (and less code = less possibility of errors).All of this, obviously in a backwards-compatible manner (in terms of API and the JS engine used), though the
async
functions would most certainly mean adding a transpiling step.