Message from JavaScript discussions

December 2018

— That depends on the caller

—  

var f = hzUserLib.hookArrowCoroutine(function*(n) {
  (yield hzUserLib.returnValue([(yield hzUserLib.add([n, (yield hzUserLib.multiply([n, n]))]))]));
});

— It does not do this currently but it is planned

— So that even the most granular atoms of an expression can be interrupted

— It means math operations from other functions could be interlaced in the time frame it takes to execute all of them

Message permanent page

— Would it be sensible to track and cache some operations?

— 

funcA(param1);
funcB(param2);


vs

funcB(param2);
funcA(param1);


may give different result and there is no way to determine automaticly

Message permanent page

— That is a pipedream but I thought of it, lol

— Let's say user calculates 3*3 10k times a second, memoization?

— That would come after the multiprocessing stage of the project, in which it has direct control over CPU cores

Message permanent page

— There are actually ways to determine it automatically, but that's not what is happening

— ^^^ determin1st