Message from JavaScript discussions

December 2018

— 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

— 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

— I could target "hot" functions and make an operand cache paired with an output cache, and the dependency analysis could inform it of whether or not it is appropriate to re-use old outputs rather than re-running a function

Message permanent page

— Yeee

— Right now I haven't gotten to the multithreading stage yet, which is required to do the multiprocessing stage

Message permanent page

— Not using labels? :(

— Maybe only target functions that run for > n chunks