> I'd rather see client patterns that are immune to callbacks being called > before the function returns sometimes.
Ditto! We should encourage people to write callers that are good, rather than libraries that deliberately waste performance and tell the callers "its alright you wrote bad code, they have to put in a process.nextTick anyway". And < 1ms can be a lot in some areas. Document your function accordingly, if it guarantees a particular callback/return order or not. In many situations, standard is, callback immediately if you have all what is needed for the callback. If the caller fucks up, that one should be fixed, instead of the callee. Or in other words, cure the problem, not the symptom. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: 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 post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
