Alex Hoppen
Alex Hoppen
Entries in call stack for Swift async functions starts with “await resume partial function for”
OS: macOS 14.0 VSCode version: 1.84.2 CodeLLDB version: 1.10.0 Compiler: swift-DEVELOPMENT-SNAPSHOT-2023-11-13-a from [swift.org](https://www.swift.org/download/#trunk-development-main) Debuggee: A Swift executable When debugging a Swift executable every async function in the call stack is...
https://github.com/apple/sourcekit-lsp/issues/611 introduced the `workspace/tests` and `document/tests` methods to lists all tests within a workspace or document. The VS Code extension should be using them to list the available tests.
Currently, when building, VS Code only shows `Building…` as an activity indicator (or whatever the thing in the bottom bar is called). It would be nice if it would show...
Instead of scraping the build log for errors/warnings/notes using a regex, it would be cleaner if the VS Code extension would read the diagnostic file emitted by `-serialize-diagnostics-path`. That way...
In the problems pane, it would be nice if we could de-duplicate errors reported by `sourcekitd` and `swiftc`. My suggestion for this would be: If `sourcekitd` reports an error at...
When an `XCTAssertEqual` fails, it would be great if we could see a diff of the actual vs expected output. That would make spotting the actual difference a lot easier.
rdar://125579439
After https://github.com/apple/swift-syntax/pull/2527, `IncrementalEdit` and `SourceEdit` are more or less equivalent types. Both store a replacement range and a replacement. The only meaningful difference is that `SourceEdit` has `String` as a...
Depends on https://github.com/apple/swift-syntax/pull/1013 and https://github.com/apple/swift-syntax/pull/1010. --- The idea is that we encode enough information as static members of the `Syntax` nodes that we can figure out which tokens are valid...