DescriptionClarify comments about the role of the lex/parse table cache action
The comment claimed the explicit cache update step wasn't required, and
explained why we still did it. This was correct for a clean build, but
for an incremental build, when stale cache files might exist, it was
incorrect; the explicit cache update step is in fact required to refresh
a stale cache.
NOTRY=true
Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=176917
Patch Set 1 #
Messages
Total messages: 5 (0 generated)
|