Until recently I have been using FSC and defined ctrl-S to the compile-file action. This way when writing a single class and its test I could just compile either file by itself -- enough to run the unit test. This was quite fast. But recently FSC started failing to compile our system. Sometimes you would have compile twice; sometimes you had to restart FSC; and then finally it simply would never compile our system. So I switched the external compiler.
Wow, what a difference. My turnaround has gone in the dumps. The external compiler (nailgun?) does not honor compile-file and insists on searching all over the code base for dependents to update. I have gone from a 1-second to compile and run the test to 10s of seconds, sometimes much more.
It seems that the external compile does not compile what is needed for the file at hand, but does also does a reverse dependency compile. This is way worse than being slow, because if I have errors in classes that depend on the class I am working with (eg, change of signature), compling the class I am working with issue errors. Yes, the errors are real. But I don't need to know that /every/ time I compile the file. I need to know that when I make the project.
So, has anybody developed any strategies to get back to compiling with pleasure when using the external compiler?