Comment 1:

Labels changed: added priority-later, removed priority-triage.

Owner changed to @adg.

Status changed to Accepted.

Comment 3 by ralph.corderoy:

A related, and perhaps simpler, enhancement would be an optional textarea for stdin.
Lots of little examples could use a few lines of accompanying text to process,
just as Unix shell examples often have a "cat foo" before the "bar <foo".

Comment 4:

Labels changed: added go1.3maybe.

Comment 5:

Labels changed: added release-none, removed go1.3maybe.

Comment 6:

Labels changed: added repo-playground.

This one seems easy enough to encourage new gophers to contribute to it, should it get a label to mark it as such?

Sure. It used to be much harder when it ran on internal Google infrastructure, but nowadays it's just a Docker container.

Don't want to be a party pooper, but do we really need to have this? I mean, it's been 6 years already and nobody wanted even to try to implement it... Would it be a game changer if we had such a feature? What about relation to go modules? I am thinking out loud just to initiate a feedback from the community.

@andybons

I'm less inclined to want this feature given that other services provide it (https://repl.it comes to mind). The maintenance burden for something like this would be very high. I would need to understand why the playground would need to be in this space to begin with. Would the impact be worth the effort?

I like that play.golang.org (and various methods of embedding it) are relatively simple implementations that are highly effective. If users wish for something more with more features, they can get it via the other tools that exist (for example, https://goplay.space/).

Multiple files seems like overkill for this product.

I wanted to implement this feature when I finished the first patch to playground. But now after some time and some more work done, I see the ratio of profit/maintenace_cost as close to zero. I appreciate the inarticulate simplicity of playground, both externally and internally.

Closing since other products do it better than we wish to at the moment.

It would've been nice for newcomers learning about testing, but using an alternative playground probably makes more sense.

It is possible to run tests and examples in Playground: https://play.golang.org/p/5Ef482JD2Lp