Support `#Playground` macro / `swift play`

[MahdiBM]

Is your feature request related to a problem? Please describe.
This is an issue to track progress on #Playground and swift play support.
I'm not sure if there is much actionable right now.

Repo: https://github.com/apple/swift-play-experimental

Describe the solution you'd like
Xcode 26 supports a #Playground macro. The VSCode extension should too.
This is helpful for quick experiments.

Describe alternatives you've considered
Live on with swift repl or swift -e. Have a "playground file" which is ignored by git and manually run it from the command palette.

Additional context
I find myself using swift repl or swift -e a bunch of times every week, and the new #Playground macro could be a better alternatives to those.

[adam-fowler]

You know you can run the current file as a Swift script regardless of whether it has been saved or not using the command run Swift script. This is how I test small Swift scripts. Otherwise I create a temporary Swift snippet if I want to test something in the current library I'm developing.

[MahdiBM]

Yeah that's what I meant by "Have a "playground file" which is ignored by git and manually run it from the command palette.".

I guess in that sense we're less in need of the #Playground macro than Xcode users since I dont recall Xcode having an option to run a single file?

[MahdiBM]

(Added a link to the swift-play repo. Forgot to paste that link when I created the issue)

[adam-fowler]

I think @compnerd started something related to integrating the repl in VSCode. It was just as I was extracting myself from VSCode dev so didn't pay too much attention.

[MahdiBM]

yeah I remember some movements around Jupyter notebook support ... not sure where that went.

[compnerd]

It didn't go anywhere AFAIK. @plemarquand seemed interested but I think that they lost interest or forgot about it.

[plemarquand]

I played with it a bit but ultimately figured a proper Swift Jupyter kernel would be a better experience