Spaceship is a high-performance systems automation language designed to replace legacy shell scripting. It features a strict, Go-inspired syntax, a powerful fixed-width type system, and a novel JIT (Just-In-Time) compilation model for POSIX commands, all built on top of LLVM.

• Performance: Statically typed and JIT-compiled for maximum execution speed.
• Security: Eliminates shell injection vulnerabilities through a strict Process API powered by direct OS-level syscalls.
• Reliability: A clear, explicit error handling model based on POSIX exit codes.
• Modern Syntax: A clean, Go-inspired syntax that is easy to read and write.

Spaceship uses a strict, fixed-width type system. There is no type inference; all types must be explicitly declared.

Spaceship uses an explicit error handling mechanism that maps directly to POSIX exit codes and errno. Any function that can fail must declare its return type with a ! prefix, indicating that it returns an error contract.

Example: fn readFile(path u8[]) !i32

• On success, the function returns a non-zero value.
• On failure, it returns a standard POSIX error code (e.g., ENOENT for "No such file or directory").

This contract is enforced by the check {} except {} block.

check {
    // Code that might fail
    var fd = readFile("my_file.txt")
} except {
    // This block executes if readFile() returns an error code
    // The error code is implicitly available in the `err` variable
    Posix.write(stdout, "Error reading file: " + err)
}

All external commands are executed using the Process API. This API is powered by a backend Syscalls runtime library that interfaces directly with the host operating system's process creation APIs (e.g., fork/execve on Linux/macOS, CreateProcess on Windows).

This is a critical security feature that prevents shell injection vulnerabilities by design, as arguments are passed as a structured array, not a raw string to be parsed by a shell.

Example: Process("ls", ["-l", "/home/user"])

Spaceship uses a deferred execution model for command pipelines, inspired by fluent APIs. Operations are chained together using .then(), but no execution occurs until .run() is called.

Example:

var pipeline = Process("grep", ["-r", "keyword", "."])
    .then(Process("wc", ["-l"]))

// Nothing has executed yet.

var result = pipeline.run() // The pipeline is now executed.

The @jit directive is a powerful compiler feature that translates shell scripts into native POSIX logic and JIT-compiles them directly into the LLVM execution path. This provides a significant performance and security advantage over traditional shell script execution.

Example: @jit("deploy.sh")

This allows developers to leverage existing shell scripts while benefiting from the performance and security of the Spaceship runtime.

The primary standard library for Spaceship is the JIT-compiled POSIX layer, along with the Syscalls runtime library. This ensures that all file I/O, process management, and other system-level operations are as fast and efficient as possible.

// Declare a fixed-size array of 4 64-bit integers
var vector [4]i64

// Declare a map with string keys and 32-bit integer values
var user_ages map[u8[]]i32

// Accessing an element (syntax)
vector[2] = 100
user_ages["jules"] = 32

// Definition for a function that can fail
fn open_or_fail(path u8[]) !i32 {
    // ... low-level POSIX call to open the file ...
    // Returns a file descriptor (i32) on success or an error code on failure.
}

fn main() {
    check {
        var file_descriptor = open_or_fail("/etc/hosts")
    } except {
        // The 'err' variable is implicitly available and holds the i32 error code.
        Posix.write(stdout, "Failed to open file with error code: " + err)
    }
}

// Find all .log files, count their lines, sort numerically, and get the top 5.
var pipeline = Process("find", [".", "-name", "*.log"])
    .then(Process("xargs", ["wc", "-l"]))
    .then(Process("sort", ["-n"]))
    .then(Process("tail", ["-n", "5"]))

// Execute the entire pipeline.
var top_five_logs = pipeline.run()

Posix.write(stdout, top_five_logs)

The primary goal of Spaceship is to provide a significant performance improvement over traditional, interpreted shell scripting languages like Bash. By using a JIT-compiler with LLVM, we aim to execute common systems administration and automation tasks an order of magnitude faster.

The following benchmark is hypothetical and serves to illustrate the performance goals of the project. The task is to count the total number of lines in all .log files within a large directory structure.

This theoretical benchmark highlights the advantages of avoiding interpreter overhead and leveraging direct, compiled POSIX calls for process management and I/O. Note : The standard library is still under development .