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
`Remove-Item -ErrorAction Ignore` silently swallows failures, which
on Windows happens whenever any file in the target tree is held by
another process (an in-flight build, an editor, virus scanning, etc.).
The result is a partially-deleted build directory: subsequent `ninja`
runs then treat the stale survivors as up-to-date, so a header API
change produces objects that link against a signature no longer present
in their dependent libraries.
Wrap each removal in a small helper that:
- skips paths that do not exist (so a first-time clean is not an
error),
- runs `Remove-Item` with `-ErrorAction Stop`, and
- on failure throws a clear message naming the path and the likely
cause.
Also correct the parameter docstring; the previous text described a
behavior that has not matched the implementation in some time.
0 commit comments