`FileManager.enumerator(at:includingPropertiesForKeys:options:errorHandler:)` does not respect `.producesRelativePathURLs` on non-Darwin

[Dadoum]

On Darwin platforms, the returned URLs have a non-nil baseURL field. On Linux that's not the case, baseURL is nil.

[Dadoum]

I think the problematic code is there: https://github.com/swiftlang/swift-corelibs-foundation/blob/main/Sources/Foundation/FileManager%2BPOSIX.swift#L407

[parkera]

@jmschonfeld is this code specific to SCL-F or was it also ported to swift-foundation?

[jmschonfeld]

@parkera the enumerator hasn't been ported to swift-foundation yet so this is SCL-F specific, probably a discrepancy between the SCL-F swift code and the underlying Foundation.framework implementation on Darwin

[jmschonfeld]

@Dadoum can you provide some sample code, the expected / actual output for the issue that you're seeing, and the Swift / OS versions that you're testing on? When trying with the latest nightly-jammy container on Linux and a recent macOS build I'm seeing that the URLs provided by the enumerator (when enumerating a directory like /tmp) are full URLs and have nil baseURL properties on both macOS and Linux. So to me it looks like the behavior is the same between both

[Dadoum]

I did indeed forget to mention an important detail, macOS generates it when the option .producesRelativePathURLs is set. On Linux this seems to be ignored, or at least with swift-6.1.3-RELEASE.

Here is my test case (change the url btw):

import Foundation

func errorHandler(_ url: URL, _ error: Error) -> Bool {
    assertionFailure((error as NSError).debugDescription)
    return true
}

let catalogURL = URL(string: "file:///home/dadoum/Projects/")!

let directoryEnumerator = FileManager.default.enumerator(at: catalogURL, includingPropertiesForKeys: [.isDirectoryKey], options: [.skipsHiddenFiles, .producesRelativePathURLs], errorHandler: errorHandler)!
for case let fileURL as URL in directoryEnumerator {
    print(fileURL.baseURL)
}

[jmschonfeld]

Ah yeah that'd be the key difference, it looks like that option is ignored here in SCL-F. Updating the title to reflect that