All current multi-sync-flow-logic stuff are actually all explicitly designed in the way so you cannot do this. That is yield a caller, without it knowing about this​ possibility and making it part of the "call contract". Every one has a highlight to say "attention this call might yield and even cause reentry", be it the "yield" keyword with generators, or the '_' streamline in Brunos stuff.
In vanilla fibers it is actually possible to yied a fiber without the caller knowing about it in the call contract, for which it has been critized. However, the caller needs to running in a fiber the first place. Brunos streamline transpiler always has been async to the bone. It just looks like sync code to the coder. So if you need to use a library that has an readFileSync included, you should easily be able to modify it only slightly to be able to through it through the transpiler to be async friendly. As long the now possible reentries don't bite it due to blowszy use of globals or upvalues. -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/CABg07fu9GeqGKKFYS0G6ORRq18uOBdjTmHRL4GvJHTKQKJYLtQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
