correct incorrect handling of file paths #6355
Open
+29
−21
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
URL.pathis not a usable rendering of the path.URL.pathrepresents the URI path. If the path is meant to be consumable as a file path, the file system representation (aka FSR) must be retrieved.Unfortunately, the FSR access is a bit more complicated as the API for that returns a +0 borrowed object with the lifetime bound to
URL. Because this relies on the toll-free bridged storage ofURL, Swift does not have this. Instead, we are provided awithUnsafeFileSystemRepresentationwhich provides a heap allocated buffer that is scoped, which we can copy into aString. To abstract away this wart, we introduce an extension onURLto access the FSR through the newfilepathproperty.This improves the file path handling and makes additional tests now pass.