Commits on May 1, 2024

1. Filter index entries for deleted source files …

   This introduces an abstraction layer around `IndexStoreDB` (yes, I known another one …) that consults the underlying `IndexStoreDB` and then checks whether the entries are up-to-date with respect to some `IndexCheckLevel`. Requests can specify how picky they want to be about declaring results from the index out-of-date.
   
   The default choice right now is to not include index entries from source files that have been deleted (because those are definitely from lingering unit files) but include results even if the source file has been modified after it was last indexed. We do include results from files that have been modified since they were last indexed because: When a file gets modified, it's likely that some of the line:column locations in it are still correct – eg. if only one line is modified and if lines are inserted/deleted all locations above are still correct. For locations that are out of date, showing stale results is one of the best ways of communicating to the user that the index is out-of-date and that they need to rebuild. We might want to reconsider this default when we have background indexing.
   
   rdar://125230833
   rdar://126622963

   

   ahoppen committed May 1, 2024
   Configuration menu

   • View commit details
   • Copy full SHA for f23d5d6
   • Browse repository at this point

   Copy the full SHA

   f23d5d6 View commit details

   Browse the repository at this point in the history