Continuous output during execution and refactoring
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 697
- Forks
- 28
- PR merge metrics
- No merged PRs in 30d
Description
Hello @Miserlou
I used loop some times for running tests etc and it's very very useful. A missing feature for me has always been that the output is not printed immediately and just after the program exits. Furthermore the stdout and stderr is merged which is sometimes bad.
I tried to fix those things but ended up with a more or less rewrite of loop based on tokio for the io and child process handling. The CLI interface is almost the same. I pushed it and I'm using it since a couple of days. I probably needs some more polishing but in general works.
Let me know if you're interested in this branch.
Thanks for the missing loop command ;-)
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 reviewing the current loop implementation and comparing it with the proposed Tokio-based branch at https://github.com/flxo/loop. Check how child-process output is handled, then verify that stdout and stderr remain separate and output appears while execution is ongoing.
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