Hi, I am working on the IntelliJ IDE plugin and after reading the roadmap, I am worried about the migration from ninja to the new rewatch build system.
all Jetbrains editors are buffering the code updates in memory, and they are not flushed to disk immediately.
To be able to have fast feedback on errors, the current workflow is that I copy the current edited file to the disk in a temporary folder.
Then I can run a ninja build command on that specific folder with all the directives or -I from the rules that I extract from the ninja build file.
It works well and I can have faster errors for a much better user experience.
It is also nice because ninja is so small and fast that I can launch a process each time and I don’t have to maintain a background process.
I have no idea what the rewatch build system is, but I am worried that such a workflow can’t be possible in the future. Not being able to process one file on demand would lower the user experience a lot.
Would that be possible ?
also, I am a big fan of insource=false.
We already have a lot of reason/rescript files and I like to hide the js files in a lib folder so that the number of files to look at are not duplicated.