abs-lang / abs

73%

master: 71%

LAST BUILD ON BRANCH background-commands

branch: background-commands

CHANGE BRANCH

x

Reset

• background-commands
• badges
• 1.1.x
• make-hashes-iterable
• destructuring-hashes
• issue-144-cd-only
• key-in-hash
• sleep
• contributing
• release-1.1.0
• 1.1.0
• master
• 1.2.x
• issue-144-v2
• issue-166
• issue-164
• issue-164-v2
• parse-exponential-notation
• absrc-source-file
• issue-171
• issue-171-alex
• mount-abs-history-in-dev
• better-illegal-tokens-when-parsing-numbers
• number-math-rounding
• issue-190
• doc-command-executor
• add-code-of-conduct-1
• 1.2.0
• 1.3.x
• bats-testing
• go-1.12
• unicode
• issue-199-exec
• 1.3.0
• 1.4.x
• underscores-in-numeric-literals
• go-mod
• hash-str-should-convert-to-valid-json
• implicit-return-value
• fix-hash-to-json
• 1.3.1
• benchmark-for-lazy-evaluation
• lazy-evaluation-in-1.3.x
• 1.3.2
• repl-without-terminal-no-panic
• eval
• allow-digits-in-vars
• 1.4.0
• 1.5.x
• negate-in
• 1.4.1
• break-continue
• higher-file-writers
• stack-overflow
• unique
• 1.5.0
• numeric-bash-arguments-support
• 1.6.x
• 1.5.1
• deprecate-legacy-command-syntax
• index-ranges
• 1.6.0
• 1.7.x
• return-semicolon
• 1.6.1
• playground
• reverse-search
• echo-dying-message
• reverse-search-2
• replace-array
• replace-short-form
• number-abbr
• index-ranges-bug
• 1.6.2
• 1.7.0
• 1.8.x
• source-vs-require
• negative-indexes
• bash-style-interpolation-in-strings
• go-prompt-master
• array-tsv
• go-1.13
• abs-installer-fixes

Build # 401

Build Type

Pull #179

travis-ci-com

Committed by web-flow

Commit Message

Experimental support for background commands, closes #70

This was easier than I though, but it required some changes here
and there.

The `String` object now has an internal mutex, used to keep hold of
the value of the command until it's executed.

What really changed is that:

* regular commands go through "normally"
* background commands are defined as commands that end with `&` (`$(sleep 1 &)`)
* background commands are launched in a goroutine and "locked" with the above mutex
* when the command is over, we set its output and release the mutex
* added the `cmd.wait()` function which will try to acquire the lock on the mutex, thus waiting until the command is done
* added the `.done` property on string to understand whether a command is done or not

Fun things that we can do now:

```
cmd = `sleep 10`
echo("This will be printed in 10s")

cmd = `sleep 10 &`
echo("This will be printed immediately")
sleep(9000)
cmd.done # FALSE
cmd.ok # FALSE
echo("We have been waiting 9s")
cmd.wait()
echo("And approximately another second")
cmd.done # TRUE
cmd.ok # TRUE
```

@ntwrick hat do you think?

Pull Request Pull Request #179: Experimental support for background commands, closes #70

Run Details

60 of 98 new or added lines in 3 files covered. (61.22%)

328 existing lines in 4 files now uncovered.

2462 of 3364 relevant lines covered (73.19%)

78.68 hits per line