Running your Config

flowchart TB
    A[Read Config] --> B[Has **redir_input** Field?]
    B --> |True| C[Pipe Input to **command**]
    C --> Z[Running Complete]
    B --> |False| D[Run **command** with set variables]
    D --> E[Used **input** variable, **command** failed, **or** has **run** field == false?]
    E --> |True| Z[Running Complete]
    E --> |False| F[**run** field is an array]
    F --> |True| G[Run **run** field with variables]
    G --> Z[Running Complete]
    F --> |False| H["Run ./{{OUT}}"]
    H --> Z[Running Complete]

Language Features

By default, if your program is Compiled, QuickerMD will infer that your program needs to be run.

When compiling certain languages, such as C, a normal workflow may look like the following:

gcc main.c -o main

This would create an executable named main. In order to run your program, you would need to run the executable.

./main

In total, at least 2 commands are required for C.

However, for newer languages such as Go and Rust, just a single command is required.

Many of these languages offer support for running your program with just a single command.

# Rust
cargo run

# Go
go run main.go

# Python
python main.py

# Zig
zig run

For this reason, QuickerMD sets the default behavior to the diagram above, to determine if the command requires another for running.