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
@nvanfleetasked on twitter whether index-import would work when syncing indexes between local checkouts, if they're not on the same git version.
This may work by adjusting the timestamp of output unit files. For example, consider importing MyFile.o-AAAAAAAAAAAA from checkout A into checkout B. If A/MyFile.swift and B/MyFile.swift have different modification times, then this index may be invalid, because A/MyFile.swift is in the future compared to B/MyFile.swift, or vice versa. To resolve this, after importing index-import could update the timestamp of the new unit (MyFile.o-BBBBBBBBBBBB) file to be be earlier than B/MyFile.swift. Xcode would hopefully see the index as being out of date, and re-index B/MyFile.swift. Source files that have matching timestamps would have their timestamp preserved.
The text was updated successfully, but these errors were encountered:
@nvanfleet asked on twitter whether
index-import
would work when syncing indexes between local checkouts, if they're not on the same git version.This may work by adjusting the timestamp of output unit files. For example, consider importing
MyFile.o-AAAAAAAAAAAA
from checkout A into checkout B. IfA/MyFile.swift
andB/MyFile.swift
have different modification times, then this index may be invalid, becauseA/MyFile.swift
is in the future compared toB/MyFile.swift
, or vice versa. To resolve this, after importingindex-import
could update the timestamp of the new unit (MyFile.o-BBBBBBBBBBBB
) file to be be earlier thanB/MyFile.swift
. Xcode would hopefully see the index as being out of date, and re-indexB/MyFile.swift
. Source files that have matching timestamps would have their timestamp preserved.The text was updated successfully, but these errors were encountered: