Live and recent posts from across the Fediverse tagged #filepath, aggregated by home.social.
Generic XCTest assertions produce vague failure messages. Building custom assertion helpers with #filePath and #line preserves accurate failure locations while producing much clearer diagnostics. Small technique with outsized value for test quality.
🔗: https://qualitycoding.org/swift-test-assertions/ by Jon Reid (@qcoding)
Can anyone point me to an online Java compiler which runs the JDK on Windows? I only find Linux systems.
I would be particularly interested in what
java.nio.file.Path.of("a/b/c")
returns on a Windows system. My hunch is that it is the same as
java.nio.file.Path.of("a\\b\\c")
because the forward slash, afair, also works as a path separator. Or is the forward slash merely a no-go character like ':' and many others?
@nicklockwood The old assertions take
file: StaticString = #filePath, line: UInt = #line
The new ones are slightly different (String and Int), plus the extra fileID & column
@polpielladev
Yeah, thats what I meant. As I have very simple Packages and the only difference between them is the name, I now use this trick to dynamically generate the name of the package from its foldername:
let name = String(#filePath.split(separator: "/").reversed()[1])
This way, all the package.swift files are identical.
TIL that how GitHub figures out syntax highlighting for Swift files is one huge plist file of 5000 lines maintained by TextMate and pulled in as a submodule into linguist. Hopefully this PR should also add proper syntax highlighting for `#filePath`: https://github.com/textmate/swift.tmbundle/pull/42