Add - as placeholder for stdin/stdout

[b1ek]

this should be useful when amber is used like this:

let amber = Command::new("amber")
    .arg("-").arg("-")
    .pipe_to_stdin("import something from \"somewhere\"\necho something(\"hi!\")\n")
    .run();
let compiled = amber.get_stdout();
do_stuff_with_compiled_bash(compiled);

also this PR adds support for /dev/null as an output destination: if it is /dev/null, the compiled code will be discared (like a dry run or something)

[arapower]

$ amber -e 'echo "abc"'

How will the above command execution change after this change?

[Ph0enixKM]

Let's add:

• --silent - silence the output. It can't be --quiet because we have a syntax in amber to silence commands silent. This will make naming unified
• --input - expects user to pass input to stdin instead of reading path. This is more readable than single - symbol.

amber --input [OUTPUT] # Outputs to a file
amber --input # Outputs to STDOUT
amber --input --silent # Never outputs

What do you think?

[b1ek]

• This is more readable than single - symbol.

the reason for using - is that many core unix programs treat it as stdin/stdout. like cat - will read from stdin

[Mte90]

I like that we offer both, - and --input as the first one is already a bash standard for this kind of stuff in various commands and the other one is more explicative.

[b1ek]

maybe we should rather just leave it as - and reserve --input for future use? it seems like a nice keyword that can refer to almost anything

[Ph0enixKM]

the reason for using - is that many core unix programs treat it as stdin/stdout. like cat - will read from stdin

I see. Okay we can use the - then. Let's still use the --silent for silencing output

[Mte90]

So to approve this PR we need just the conflicts fixed?

[Ph0enixKM]

@b1ek To merge this let's:

• Modify the code to use the --silence instead
• Resolve conflicts

[Mte90]

So I tried to align the code to the latest changes, also added --silence so we can have both (also -) but I am not sure if works.

There aren't tests or how to use it.

[Ph0enixKM]

@Mte90 sorry. It should be --silent. I made a mistake in my previous comment.

[Ph0enixKM]

@Mte90 I clarified what I meant

[Ph0enixKM]

Use case scenarios for the CLI:

• amber file.ab -> Runs the code and outputs
• amber file.ab - -> Outputs the compiled bash code
• amber file.ab file.sh -> Compiles the code to the destination
• amber --silent file.ab -> Performs a dry run of compiler and the amber script
• amber --silent file.ab - -> Performs a dry run of the compiler

[b1ek]

it will still break if the user uses /dev/null as the output file

[Ph0enixKM]

Typo

[Ph0enixKM]

Resolved conflicts

done