# Glyim > Documentation for Glyim, a modular, from-scratch compiler for a Rust-like systems programming language, written in Rust. Source: https://github.com/elcoosp/glyim ## Tutorials - [Getting Started with Glyim](https://vercel.app/tutorials/getting-started.md): Build the Glyim compiler from source, scaffold a project with glyip, and run your first Glyim program end to end. ## How-to Guides - [Build and Run Your Project](https://vercel.app/guides/build-and-run.md): Use glyip build and glyip run to produce debug and release builds, choose a backend, set optimization levels and LTO, and pass arguments to your program. - [Manage Dependencies](https://vercel.app/guides/manage-dependencies.md): Declare path, registry, and git dependencies in Glyip.toml, understand the lockfile, and diagnose resolution conflicts. - [Test Your Code](https://vercel.app/guides/test-your-code.md): Run tests with glyip test, choose between the MIR interpreter and compiled native executables, annotate expected errors inline, and bless snapshot changes. - [Inspect the Compilation Pipeline](https://vercel.app/guides/inspect-compilation.md): Use glyim to emit MIR, LLVM IR, assembly, or object files, tune optimization and codegen units, read diagnostics as JSON, and adjust lint levels. - [Use the Language Server](https://vercel.app/guides/use-the-lsp.md): Run the glyim-lsp language server and integrate its diagnostics, navigation, and code actions into your editor workflow. - [Write GSX Views](https://vercel.app/guides/write-gsx-views.md): Author typed GSX view elements with directives, keyed iteration, and two-way bindings, and run them through the glyim-gsx compiler stage and headless test host. ## Reference - [glyim CLI Reference](https://vercel.app/reference/cli.md): Every flag of the glyim compiler driver — emit kinds, backends, optimization, LTO, targets, diagnostics formats, the standard library prelude, and lint levels. - [glyip Reference](https://vercel.app/reference/glyip.md): The glyip build tool commands and the complete Glyip.toml manifest schema — package metadata, targets, and dependency declarations. - [Language Reference](https://vercel.app/reference/language.md): The Glyim language — declarations, types, traits, pattern matching, closures, async/await, macros, and compiler-known builtin types. - [Lint Reference](https://vercel.app/reference/lints.md): The compiler lint framework — available lints, their aliases, severity levels, and the -A/-W/-D command-line flags. - [Crate Reference](https://vercel.app/reference/crates.md): Every crate in the Glyim Cargo workspace and its role in the compilation pipeline. - [GSX Reference](https://vercel.app/reference/gsx.md): The GSX view syntax and the glyim-gsx compiler stage API — grammar, directives, regions, blueprints, hosts, and diagnostics. ## Explanation - [Architecture](https://vercel.app/explanation/architecture.md): Why Glyim is split into more than 30 single-responsibility crates, and how that makes every phase testable in isolation. - [The Compilation Pipeline](https://vercel.app/explanation/pipeline.md): A stage-by-stage walkthrough of what happens between source.g and a native binary or bytecode program. - [Borrow Checking](https://vercel.app/explanation/borrow-checking.md): How Glyim's NLL borrow checker works — Polonius-style region inference, cross-block liveness, two-phase borrows, move analysis. - [Ownership-Driven Reactivity](https://vercel.app/explanation/gsx-reactivity.md): How GSX uses the borrow checker's read/write sets instead of a virtual DOM — skeletons, slots, mutation-specialized patches, and the cost model. - [The Testing Model](https://vercel.app/explanation/testing-model.md): Why the compiler ships five test modes, phase mocks, snapshots, and property tests — and how each layer catches a different class of bug. ## Optional - [How we built a 39-crate compiler with two backends](https://vercel.app/blog/welcome-to-glyim.md)