Swift Extension Community Office Hour - August 7 2026

[matthewbastien]

Hello everyone!

We'll be hosting another community office hour for the Swift extension for VS Code in August.

Event Details:
Hosts: @matthewbastien
When: Friday, August 7, 2026 1PM EDT
Where: DM for Webex invite

Agenda:

• What’s new in VS Code - @matthewbastien
• Demo: Go to definition and diagnostics for SwiftDocC - @padmashree06
• Talk: Improvements to LLDB on Windows - @c_zablit
• Open up to Q&A

Everyone is welcome, so please feel free to invite anyone you think might be interested. This is a laid-back space to ask questions, share experiences, and learn from each other—whether you're an experienced developer or just starting out.

Please note that we expect members joining to adhere to Swift's Code of Conduct.

See you all there!

[matthewbastien]

Thank you to all who attended and to @padmashree06 and @c_zablit for demoing! Here are the minutes from the meeting:

Demos:

• @padmashree06 is a GSoC 2026 contributor demoing her work so far on extending SwiftDocC support in SourceKit-LSP
  • Go to Definition in Swift documentation comments, Tutorial, and Markdown files
  • Diagnostics for broken DocC symbol links
  • Syntax highlighting for directives in Markdown and Tutorial files
• @c_zablit talked about recent improvements to LLDB on Windows
  • Support for the PDB format that WinDBG uses natively
  • LLDB is now using ConPTY on Windows to support running in the integrated terminal in VS Code. This fixes a long-standing issue with readline on Windows
  • The LLDB DAP extension in VS Code will now let you know if you need to install Python.
  • Future versions of LLDB will support multiple Python versions on Windows, reducing the need to install such a specific version.

Q&A Session:

• Q: Can we support underlining/better syntax highlighting within Swift documentation comments to better advertise the go to definition feature?
  • A: This is a fantastic idea! We're not sure about how feasible it would be for the syntax highlighting (VS Code supports a very specific list of tokens that might conflict with the look and feel of normal comments). An underline might be feasible. We will definitely have a look at implementing this.
• Q: How are the documentation symbol links actually handled?
  • A: SwiftDocC tries to find the symbol name by looking at the smallest scope that the reference is contained within to try and find the most appropriate symbol based on the provided name. In the case of collisions it allows you to specify the containing symbol using forward slashes (e.g. Foo/bar()). There are other disambiguations that you can read about in SwiftDocC's documentation. The implementation for go to definition in SourceKit-LSP uses the symbol graphs and index to resolve symbol names.
• Q: In what version of the Swift toolchain will the latest LLDB changes be available?
  • A: Today's demo was using a local mainline build of the Swift toolchain. The next main snapshot build will contain all of the features from today's demo.
• Q: What difficulties do you foresee with future improvements to LLDB on Windows?
  • A: The PDB format is closed source and was built primarily for C based languages. It does not support a lot of the fancy features that Swift does (e.g. generics). If there isn't sufficient overlap then we plan on adding special syntax to PDB that, to a normal debugger like windbg, would just look like a comment and be ignored. However, LLDB will be able to read that format and provide additional information.
• Q: Now that LLDB supports better formatting for many of the std:: C++ types, will we be doing the same for Swift?
  • A: This has been supported on macOS for a while, but there was an issue on Windows where some types from FoundationEssentials were not getting formatted properly. This should be fixed in the latest nightly main snapshot builds.