mirror of https://github.com/sbt/sbt.git
6565618a15
The continuous command recompiles the setting graph into a CompiledMap data structure so that it can determine which files it needs to transitively monitor during watch. Generating the CompiledMap can be very slow for large projects (5 seconds or so on my computer in the sbt project) and this startup cost is paid every time the user enters a watch with `~`. To avoid this, we can cache the compile map that is generated during the initial settings evaluation. The only real drawback I can see is that the compiled map is guaranteed to remain in memory so long as the BuildStructure instance that holds it is alive. Given the performance benefit, this seems like a worthwhile tradeoff. |
||
|---|---|---|
| .. | ||
| DagSpecification.scala | ||
| HListFormatSpec.scala | ||
| KeyTest.scala | ||
| PMapTest.scala | ||
| SettingsExample.scala | ||
| SettingsTest.scala | ||
| UnitSpec.scala | ||