Should there be some way to check if the compile time options (such as debugging, yieldLimit, etc.) are the same as the runtime options when you use these compiled files? And at least print some sort of warning? Otherwise, if you mix aot and run-time compiled code, you might get unexpected results. Or do you feel like this is a "use at your own risk" feature? (In which case, perhaps that should be made really clear...)

(I'm also not totally convinced that ahead-of-time compilation is the solution to the "pain" of including extra Python files. Arguably, that's a deficiency of the documentation. If you drop them in the lib folder, for instance, it "just works" - assuming, of course, that Skulpt supports the features that they are trying to use. Just an aside, not an argument against the pull request.)

It may be something people are looking for, it doesn't break anything in our default workflow does it?

@rixner - absolutely. Ahead-of-time compilation is not the solution to the pain of bundling extra python files - ./m combineall is.

(And it is a pain - right now the only way to add them to the build is to either copy them into the Skulpt source tree(!!), or roll your own Sk.builtin.read() implementation - which is what Anvil does, but it's a pain for new users.)

Should I separate out AOT compilation from combineall? I agree AOT has issues with build options. (Also, it creates really big .js files)