You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 3e2db51
Browse filesBrowse the repository at this point in the historyBrowse files
Do not parse a changed file when the outcome cannot add anything
restore() parses every changed file to compare its exported nodes with
the cached ones, which decides whether its dependents, the classes using a
trait it declares, and the files with errors are re-analysed too. When all
of those files changed themselves and are re-analysed anyway, the answer
cannot add anything, so the file is not parsed.
After a branch switch or a formatting run that touched most of the project
that is most of the changed files. On Drupal core with every file edited,
restoring took 9 seconds of parsing in the main process, and the workers
forked from it were slower too. The files re-analysed stay the same.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GdwtgiEHwkF5BTz73jgHQQ
0 commit comments