btw: they're actual screen capture, not PhotoShopping...
If this preserves execution order etc etc, I'm all for it :).
yeah, I know that I should have attach testing code against this feature, but quickly go though the test folder, it seems not easy to write formed unit test code for this async like behavior into existing structure, any suggestion would be great, or should I make one test page on jsFiddle maybe?
Yes, I'm afraid we don't have tests for this kind of stuff (and I'm not even sure how we should do it)
Hi, in order to make it easy to test, I've made a Cherry Pick from this PR onto HEAD @566a7da, which after v1.6.2 yet right before the module.exports got introduced from sourcemap.litcoffee, that breaks browser execution up to now, so please feel free to check it out at this branch, thanks.
Great idea -- but the implementation looks a bit over-complicated to me. Can we simplify a bit before merging?
@imcotton: I'm not sure I understand your comment. Are you saying that 5496a18 broke something for you? Or are you implying that it wasn't sufficient to allow you to rebase off master?
@michaelficarra I mean before I start working on this, due to PR #2934 not yet been merged into master, so it couldn't get to run in the browser for testing purpose. And now I've tested with latest master branch, it is working now, so I don't know either your guys prefer rebase or merge to master on my side before this PR got picked up, thanks.
@jashkenas The code it now has get simplified, and I've performed rebase to current master HEAD @2e40864 for this PR, please let me know if there's still something left, thanks!
parallelized script loading in browser, yet order remain
remove logic redundancy
simplify logic and changing less from before
rebuild for PR #3012
include rebuilt lib/coffee-script/browser.js, and rebased against latest master branch.