Slynx

Experimental UI language workspace focused on the frontend and middleend of the language.

Slynx is an experimental programming language project for user interfaces. The long-term direction is to expose a reusable IR that downstream compilers can consume, but the current repository is primarily a library-first workspace for the language frontend and middleend.

Current Status

Slynx is still experimental and under active design.

What is true on the current main branch:

• the workspace is library-first; there is no official CLI binary target in main right now
• the root crate can lex, parse, build HIR, run type checking, resolve the current alias surface, and lower source files into SlynxIR
• the root library can write the default .sir output and can expose .hir / .ir dumps through SlynxContext::build_stages()
• sample .slynx sources live under slynx/
• the IR design is still evolving, and the design reference in middleend/README.md is broader than what main emits today

Workspace Layout

The repository is currently split into these crates:

• common/: shared AST types and common language data structures
• frontend/: lexer, parser, HIR generation, and type checking
• middleend/: SlynxIR and IR/lowering work
• src/: root library glue (SlynxContext, compile helpers, error presentation)

What Exists Today

The current codebase already includes:

• lexical analysis and parsing for core language constructs such as functions, objects, components, aliases, tuple literals/types, and control flow such as if and while
• HIR generation and name resolution
• type checking, type inference, and monomorphization for the current supported alias surface
• library entry points for compiling to IR or inspecting HIR/IR dumps before writing output
• lowering to the current SlynxIR
• CI, release, governance, and contribution documentation

The current repository does not ship an official backend crate or an official CLI binary on main.

Getting Started

Prerequisites

• Rust stable
• Cargo

Build and Validate the Workspace

git clone https://github.com/Slynx-Language/slynx.git
cd slynx
cargo build
cargo test
cargo fmt --all -- --check
cargo clippy --all-targets --all-features -- -D warnings

Using the Library Today

The root crate currently exposes helper functions for lowering a .slynx file into IR:

use std::path::PathBuf;

fn main() -> color_eyre::eyre::Result<()> {
    let ir = slynx::compile_to_ir(PathBuf::from("slynx/component.slynx"))?;
    println!("{ir:#?}");
    Ok(())
}

If you want to inspect intermediate dumps before writing output, the root context also exposes stage building:

use std::{path::PathBuf, sync::Arc};

fn main() -> color_eyre::eyre::Result<()> {
    let context = slynx::SlynxContext::new(Arc::new(PathBuf::from("slynx/booleans.slynx")))?;
    let stages = context.build_stages()?;

    println!("{}", stages.hir_text());
    stages.write_hir()?;
    stages.write_ir()?;

    let output = stages.into_output();
    output.write()?;
    Ok(())
}

Today:

• compile_code(...) and SlynxContext::start_compilation(...) write the default sibling .sir file
• build_stages() lets callers inspect or persist .hir and .ir dumps through the library API
• there is still no polished CLI workflow for dump generation on main

Example Sources

Real samples that match the current repository syntax live under slynx/, for example:

• slynx/component.slynx: basic component construction
• slynx/objects.slynx: object construction and field mutation
• slynx/while.slynx: while loops
• slynx/functioncall.slynx: typed function calls

One small component example:

component Header {
    Div {
        Icon {
            src: "https://github.icon.this.url.does_not_exist.com"
        }
    }
}

component Footer {
    Div {
        Text {text: "Footer of page"}
    }
}

component Main {
    Div {
        Text {text: "Main Part"}
    }
}

component Website {
    Div {
        Header {}
        Main {}
        Footer {}
    }
}

func main(): Component {
    Website {}
}

Documentation Map

Core project documents:

• CONTRIBUTING.md: contribution workflow and validation expectations
• GOVERNANCE.md: project roles and decision structure
• CODE_OF_CONDUCT.md: community behavior expectations
• RELEASING.md: how repository tags and GitHub Releases are cut
• CHANGELOG.md: repository-level changelog
• docs/language-surface.md: grounded overview of the current language syntax and constructs
• docs/first-slynx-file.md: short tutorial-style example for new contributors
• middleend/README.md: IR design/specification reference
• docs/issue-reporting.md: guide for opening clear, actionable issues
• docs/landing-content-inventory.md: grounded inventory of what can already be published on the landing page

Operational templates:

• .github/pull_request_template.md
• .github/ISSUE_TEMPLATE/bug_report.md
• .github/ISSUE_TEMPLATE/feature_request.md
• .github/ISSUE_TEMPLATE/documentation.md
• .github/ISSUE_TEMPLATE/discussion.md

Releases and Versioning

The repository currently has a public tag, v0.0.1, created on 2026-03-21.

At the time of writing, there is still no published GitHub Release page for that tag:

• GitHub Releases
• Git tags

For the release process itself, see RELEASING.md.

Contributing

Contributions are welcome, especially in these areas:

• frontend/parser/type-checker work
• IR and middleend design
• tests and regression coverage
• documentation and specifications

Start with CONTRIBUTING.md before opening a PR.

Community

• GitHub Issues
• GitHub Discussions
• Discord Server

License

This project is licensed under the MIT License. See LICENSE for details.