From d91fbb5c3a74ccf862202e28b3855af0eae7cc47 Mon Sep 17 00:00:00 2001 From: "Alex A. Naanou" Date: Wed, 10 Oct 2018 15:05:57 +0300 Subject: [PATCH] notes... Signed-off-by: Alex A. Naanou --- walk.js | 10 +++------- 1 file changed, 3 insertions(+), 7 deletions(-) diff --git a/walk.js b/walk.js index c1f5b5f..e5a0879 100644 --- a/walk.js +++ b/walk.js @@ -27,13 +27,9 @@ // NOTE: state can not be a function... // // -// XXX Q: should next('queue', ...) return a promise??? -// ...currently I think no, there is no need to complicate things as -// the getter will eventually get all the queued nodes anyway and -// done(..) will get called when everything processed... -// XXX this is essentially a version of .reduce(..), I wonder if it is -// feasible to do a version of .map(..), i.e. a mechanism to modify/clone -// the input tree... +// XXX this is essentially a version of .reduce(..) +// ...is feasible to do a version of .map(..), i.e. a mechanism to +// modify/clone the input tree??? // XXX can we hint chrome to show the two function singatures??? // XXX need to remove the restriction of not being able to pass functions // into state unless done(..) is given...