implement a proper REPL
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 6.6k
- Forks
- 1.7k
- Avg merge
- 16h 14m
- Merged PRs (30d)
- 1
Description
Thursday Oct 17, 2013 at 02:38 GMT
For earlier discussion, see https://github.com/rust-lang/rust/issues/9898
This issue was labelled with: A-an-interesting-project, E-hard in the Rust repository
It shouldn't re-compile and re-run the entire input so far with each new addition, and should be able to recover from a compilation error or failure. This should likely be implemented in a separate repository until it's solid and has a working test suite.
A good basis for the design would be the cling REPL for C++ built on top of libclang using LLVM's JIT compiler.
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
Start by reading the earlier discussion in Rust issue #9898 and reviewing the cling REPL reference linked in this issue. The work is complete when the REPL avoids recompiling and rerunning all prior input, recovers from compilation errors or failures, and has a working test suite, potentially in a separate repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100