Replies: 1 comment 1 reply
-
There's |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The BSP client often sends batches of requests all at once. For instance, Metals sends a
buildTarget/scalaMainClasses
abuildTarget/scalaTestClasses
and abuildTarget/jvmRunEnvironment
requests after each compilation. Processing each request sequentially takes time. We could save quite a lot of time if sbt could merge and process the requests in a single task graph.The idea would be to introduce a new command that takes a list of tasks and run them sequentially in the same task graph, merging the common parts of the graph. This would only work if the tasks don't have side effects. For instance running
clean & compile & clean
in the same task graph (the second clean is a no-op) is not the same thing as runningclean; compile; clean
.Beta Was this translation helpful? Give feedback.
All reactions