vxc: a program that vxc runs gets no standard input

Open Beginner friendly
#3,236 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
82/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
rust
Domain
cli

Research direction

Start in src/jit.rs, where the issue says vxc runs compiled programs with Command::output(). Check how the test runner launches programs so its /dev/null stdin behavior is preserved. Done means piped input reaches a program launched by vxc, its output appears while it runs, and the test runner can still use /dev/null.

Written by the indexing model from the issue text.

Description

bug devex

vxc program.vx compiles and runs the program, but the program gets no standard input. src/jit.rs runs it with Command::output(), which connects stdin to /dev/null.

$ printf 'a\nb\n' | vxc count_lines.vx
0 lines

Command::output() also holds all output of the program until the program ends. A long program shows nothing while it runs.

The program must inherit stdin. The test runner can still give it /dev/null.

Dominant language
Rust
Stars
35
Forks
5
Avg merge
12h 26m
Merged PRs (30d)
799

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from vx-lang/Vx

All issues in vx-lang/Vx

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.