dropped queue-tick in favour of queueMicrotask

[telamon]

No description provided.

[mafintosh]

Nice, its time

[ThaUnknown]

out of personal curiosity, why was queue tick, aka process.nextTick with fallback used in the first place, instead of just raw queueMicrotask? was this for backwards compabitility, or for supporting older versions?

[telamon]

The unqualified answer: i suspect queue-tick predates availability of a uniform queueMicrotask().

I had the unfortune to discover that process.nextTick() corrupts the callstack.
This patch was produced in response.

[ThaUnknown]

predates availability

it likely doesn't, qm was introduced in node11 and chrome70, when I originally PR'ed qm as a replacement to nextTick, they were widely available, the nexttick || qm fallback was added later, I always assumed because of some weird compatibility reason, where nextTick was required, seems like that was wrong?

[telamon]

@ThaUnknown by the sound of it I was twice unlucky. :'-)

This issue left me scratching my head for some time until nextTick proved to be the culprit:

https://github.com/telamon/native-addon/blob/83dd327c761596c87e6efb1885402a9e725c65dc/test.js#L52

[mafintosh]

The answer is compat