Skip to content

Commit d87ae6a

Browse files
committed
[Gardening] Remove Outdated Advice About -### and -incremental
Using -### is insufficient to discover the entire set of frontend jobs needed to satisfy a given incremental compilation session because of the presence of additional waves of recompilation. More concretely, any additional compilation jobs whose queueing behavior depends on the set of jobs reported by -### are, by definition, hidden from -###. Note that it is also *not* possible to run the incremental build to a fixpoint by iteratively executing said frontend jobs and re-running the driver with -### because the build record is never updated to account for the jobs executed by an external system.
1 parent 041dfb9 commit d87ae6a

File tree

1 file changed

+0
-9
lines changed

1 file changed

+0
-9
lines changed

docs/Driver.md

Lines changed: 0 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -294,15 +294,6 @@ past that, so:
294294
All the same options from above apply, but you'll have to manually deal
295295
with the work the compiler would have done automatically for you.
296296

297-
- Invoke `swiftc -c` with `-###`. Then run all of the outputted commands
298-
that include `-primary-file`, then run the remaining commands in order
299-
(they may have dependencies). If none of the commands have `-primary-file`
300-
in them, they're not parallelizable, sorry.
301-
302-
This is the most hacky approach, because (a) it involves looking for an
303-
internal flag in a non-stable interface, and (b) you don't get anything
304-
incremental out of this. We could stand some improvements here.
305-
306297
Whatever you do, do *not* invoke the frontend directly.
307298

308299

0 commit comments

Comments
 (0)