Take a look: https://blog.area9lyceum.com/area9-open-sources-flow-program...

It means compiler caches results of module compilation and reloads them if module didn't change. Hot code reloading is not supported.

We have some support for concurrency in Java and JavaScript backends, see lib/sys/concurrent.flow.

You need to rebuild QtByteRunner. Cd to platforms/qt/. There is a readme there for full explanation, but in short:

- clone asmjit (https://github.com/area9innovation/asmjit.git) into platforms/common/cpp folder first (eventually we'll move to upstream asmjit, we use our copy of this lib yet);

- make sure you have Qt 5.12.0 (or upper) available in your system;

- review paths in QtByteRunner.pro, they're usually fit our needs, but in some cases may require changes;

- run build.sh, it'll produce binary for your system.

Then you'll be able to run flowcpp tool.

The call chain is:

- you run flowcpp and feed it with .flow file;

- flowcpp see that it is source file and calls compiler

- compiler produces .bytecode file

- flowcpp executes .bytecode file and runs file you called.

You can call compiler directly with flowc or flowc1 commands.

Great, thanks for the explanation!