Folks are welcome to try various incremental compilation ideas. I'm not sure you can guarantee a benefit in all cases when compiling from the command-line because you still may have to parse every file that is a dependency or encode/save/reload some sort of state cache. There should be ways to get a benefit when compiling from an IDE because the IDE is your state cache and the compiler has some hooks for that. But the old Flex MXMLC algorithm had bugs so I'm not sure I would borrow from that.
BTW, I ran across another jumble which is how much code is run in IdentifierNode.resolve. I have often wondered why it must be so complex and whether passing context around would help. Or prioritizing project scope class lookups over multiname lookups. -Alex On 6/17/19, 1:09 AM, "yishayw" <[email protected]> wrote: Without knowing much about the compiler, what about incremental compilation? Can gains be made by checking for source update timestamps and making a decision as to whether or not to transpile based on that? -- Sent from: https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-development.20373.n8.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com%7Cdb2b5c9e69a64cb8137a08d6f2fb2063%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963557726154820&sdata=DorMV4v6H%2Bh4rcLM4Xp%2FydqX335SGqhwvN2UtGLvCaQ%3D&reserved=0
