Async functions should call the callbacks asynchronously about memory-fs

[sokra]

yep, callbacks should be invoked with process.nextTick. PR?

[dead-claudia]

Shouldn't they be deferred with setTimeout? I/O callbacks are scheduled
as macrotasks, not microtasks.

On Wed, Sep 7, 2016, 13:11 Tobias Koppers [email protected] wrote:

yep, callbacks should be invoked with process.nextTick

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#22 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AERrBN-NldzQjPMIlAVUqdpTbj1BAYdhks5qnvAmgaJpZM4I0B1D
.

[sokra]

We are not emulating a filesystem. So it's here just async for the APIs sake.

[dead-claudia]

I know it's not a full file system emulation. I'm just pointing out
semantics (people might rely on the macrotask semantics, in which
scheduling a microtask would break their code).

On Wed, Sep 7, 2016, 15:10 Tobias Koppers [email protected] wrote:

We are not emulating a filesystem. So it's here just async for the APIs
sake.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#22 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AERrBFe7DtQhS6xtjSVIN6Vaz_rFZ8aBks5qnwwPgaJpZM4I0B1D
.

[sokra]

Could be an issue... You are right.

Than it might be better to use setImmediate instead. @gajus