rust-lang / rust-lang/rust-playground
Spawn a playground instance per Rust PR merged
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.4k
- Forks
- 267
- Avg merge
- 3h 2m
- Merged PRs (30d)
- 6
Description
It could be useful to spawn an instance of the playground for a specific rust PR, especially for the more user-facing of changes.
Testing out and easily showing others, concrete changes to ergonomics, or similar — work about NLLs, chalk/traits, self method calls, macros, @mbrubeck mentioned testing the #[async] / generators branches as well — before they're integrated in nightly could be very helpful.
As anecdote, Babel.js seems to have such a feature, an instance of their REPL built per PR, and they seem very happy about it :)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by mapping how rust-playground builds and deploys instances, then define the PR-triggered lifecycle and verify that a merged Rust PR can expose a matching playground instance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100