Skip to content

Conversation

@award999
Copy link
Contributor

@award999 award999 commented Nov 17, 2025

Description

Can warn that they need to fully quit if the toolchain was installed while VSCode was open

Issue: #1937

Tasks

  • [ ] Required tests have been written
  • Documentation has been updated
  • Added an entry to CHANGELOG.md if applicable

Can warn that they need to fully quit if the toolchain was installed while
VSCode was open

Issue: swiftlang#1937
The Swift extension automatically detects installations of the Swift toolchain in your environment. It looks for a `swift` binary available in `PATH` and, if one cannot be found, prompts you to [install a toolchain from Swift.org](https://www.swift.org/install).

<div class="warning" markdown="1">
If you install a toolchain or Swiftly while VS Code is open, you likely will need to fully quit VS Code and then reopen it. This makes sure the extension host gets the updated PATH so that extension can find the toolchain.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: remove the ambiguity

Suggested change
If you install a toolchain or Swiftly while VS Code is open, you likely will need to fully quit VS Code and then reopen it. This makes sure the extension host gets the updated PATH so that extension can find the toolchain.
If you install a toolchain or Swiftly while VS Code is open, fully quit VS Code and then reopen it. This makes sure the extension host gets the updated PATH so that extension can find the toolchain.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah shoot only saw suggestion after merge, I'll put it into another PR

@award999 award999 merged commit e00f2c0 into swiftlang:main Nov 17, 2025
24 of 25 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants