Skip to content

Simplify a few API calls in FSProxy #427

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 24, 2025
Merged

Conversation

jakepetroules
Copy link
Collaborator

These now go through Foundation rather than Win32 APIs directly. This simplifies Unicode and long path handling in particular.

For realpath I left the POSIX implementation in place for non-Windows for now since it's not clear that has equivalent behavior. touch/setFileTimestamp now differ in that they no longer set atime, but virtually nothing uses atime.

@jakepetroules jakepetroules added the windows Support for the Windows platform label Apr 21, 2025
@jakepetroules
Copy link
Collaborator Author

@swift-ci test

@jakepetroules jakepetroules enabled auto-merge (rebase) April 21, 2025 22:07
@jakepetroules jakepetroules force-pushed the win32-api-usage-fsproxy branch from 7c9a5f3 to ab1e889 Compare April 22, 2025 00:55
@jakepetroules
Copy link
Collaborator Author

@swift-ci test

@jakepetroules jakepetroules force-pushed the win32-api-usage-fsproxy branch from ab1e889 to 6633142 Compare April 24, 2025 03:07
@jakepetroules
Copy link
Collaborator Author

@swift-ci test

@jakepetroules jakepetroules force-pushed the win32-api-usage-fsproxy branch from 6633142 to e42301e Compare April 24, 2025 04:37
@jakepetroules
Copy link
Collaborator Author

@swift-ci test

@jakepetroules jakepetroules force-pushed the win32-api-usage-fsproxy branch from e42301e to addb855 Compare April 24, 2025 16:53
@jakepetroules
Copy link
Collaborator Author

@swift-ci test

These now go through Foundation rather than Win32 APIs directly. This simplifies Unicode and long path handling in particular.

For realpath I left the POSIX implementation in place for non-Windows for now since it's not clear that has equivalent behavior. touch/setFileTimestamp now differ in that they no longer set atime, but virtually nothing uses atime.
@jakepetroules jakepetroules force-pushed the win32-api-usage-fsproxy branch from addb855 to 3cc21fb Compare April 24, 2025 20:17
@jakepetroules
Copy link
Collaborator Author

@swift-ci test

@jakepetroules jakepetroules merged commit e2f5506 into main Apr 24, 2025
3 checks passed
@jakepetroules jakepetroules deleted the win32-api-usage-fsproxy branch April 24, 2025 20:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
windows Support for the Windows platform
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants