binpash / binpash/pash

Parallelize the call to the compiler with the execution of the command

Open
#641 0 comments 0 reactions 0 assignees View on GitHub
enhancement low-priority
Dominant language
Shell
Stars
601
Forks
52
PR merge metrics
No merged PRs in 30d

Description

We could improve pash by at the same time calling the compiler and start to execute the original command.

This would give some benefits (if done fast---which seems very hard) for scripts where command execution is so small that it ends even before the compiler finished its invocation.

Below follows a solution schematic from an early prototype:
```python
## Solution Schematic:
##
## (A) (B) (C) (D) (E)
## stdin --- tee --- eager --- seq.sh --- eager --- OUT_SEQ
## \ (F)
## \--- eager --- PAR_IN
##
## (1) If compiler fails, or sequential is done executing:
## - cat OUT_SEQ > stdout
##
## (2) If compiler succeeds:
## - USR1 to reroute so that it redirects to /dev/null
## - PAR_IN redirect to par stdin.
```

Contributor guide

No contributing guide indexed for this repository

Research direction

No implementation files, tests, or entry points are named. Start by locating the compiler invocation and the execution path for the original command, then compare them with the schematic in the issue. Done means both can proceed concurrently, compiler failure or early sequential completion preserves stdout, and compiler success reroutes input as described.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell
Domain
cli, compilers, performance
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.