Home

Language

Pattern Matching Exhaustive match with guards and destructuring. Type System Inference, unions, null safety, Result types. Generics Monomorphized generics with trait bounds. Traits Shared behaviour without inheritance. Error Handling Errors as values, propagated with try.

Systems

Memory Model Ownership and borrowing, no collector. Comptime Run real code during compilation. Concurrency Async, await, channels and tasks. FFI Call C without a binding generator.

Toolchain

TypeScript Compiler home tsc checks and emits TypeScript. Macros Hygienic macros over the real AST. Editor & CLI Tooling LSP, formatter, test runner, package manager.
Every language, codegen and tooling row, with status. Capability matrix

Build with Home

Systems Programming Native binaries with predictable latency. Game Development Frame budgets without collector pauses. Operating Systems Freestanding builds, no runtime required.

Ship with the toolchain

Web Services HTTP servers and databases in one binary. CLI Tools Single-file distribution, fast start. TypeScript Migration Type-check today, move code when ready.
Guide
Standard LibraryArchitectureCompiler PipelineConfigurationDX CommandsPackage Management
Capability MatrixTypeScriptNode.jsBunRoadmap

Editor and CLI Tooling

Copy page
Copy page as Markdown for LLMs
View as Markdown
View this page as plain text
Open in ChatGPT
Copy content and open ChatGPT
Open in Claude
Copy content and open Claude
Open in Perplexity
Search with Perplexity AI
On this page 7

Home treats the toolchain as part of the language. The formatter, test runner, language server, documentation generator and package commands all ship in the same binary as the compiler, so there is one thing to install and one version to keep straight.

The daily loop

home dev              # watch and rebuild
home fix src/         # format and apply safe fixes
home test             # run the test suite
home check src/       # type-check without building

home dev runs the dev script from home.toml when there is one, and otherwise watches src/main.home or src/main.hm.

home fix walks the tree for .home and .hm files, formats them, and applies the auto-fixes that cannot change behaviour. It is the command to wire into a pre-commit hook.

Understanding a codebase

home symbols src/                     # list public declarations
home docs src --out docs/API.md       # generate Markdown API docs
home api-diff old.d.hm new.d.hm       # compare public API surfaces
home size zig-out                     # report build output sizes

home api-diff reads Home declaration files, the .d.hm format that carries package API metadata. It reports additions and removals between two versions, which is what you want in a release checklist rather than a diff of the whole source tree.

Diagnostics you can ask about

Every diagnostic has a code, and every code can be explained without leaving the terminal:

home explain T0001
home explain TS2345

Both Home's own Txxxx codes and the TypeScript TSxxxx codes are covered. The same explanations back hover in the editor.

Language server

home lsp --stdio

home lsp --stdio is the stable editor entrypoint. 76 of roughly 80 protocol methods are routed:

  • Navigation: definition, declaration, type definition, implementation, cross-file references, document and workspace symbols
  • Editing: completion with resolve, signature help, rename with prepare-rename, linked editing ranges, formatting and on-type formatting
  • Display: hover, semantic tokens including delta and range, inlay hints with resolve, code lens, document links, folding and selection ranges, document colour
  • Structure: call hierarchy and type hierarchy, both directions
  • Diagnostics: publish-based and pull-based, plus workspace diagnostics

Known gaps: quick-fix breadth is partial. Organize imports, add import and add explicit type annotation have landed; fix-all, missing return type and infer parameter types have not. Push diagnostics are not yet driven by filesystem events, formatDocument currently returns the source unchanged, and auto-import completion does not yet search the cross-file interner.

Packages and toolchain

Home reuses Pantry rather than growing a second ecosystem manager:

home pkg tools          # what the project pins
home pkg search http    # find a package
home pkg info zig       # inspect one
home pkg audit          # check for advisories
home pkg dedupe         # collapse duplicate versions

Because Pantry pins toolchains as well as libraries, the Zig version the compiler is built against lives in the project rather than on the machine. A fresh clone plus pantry install gets the exact toolchain.

Editor extensions

The VS Code extension lives in packages/vscode-home in the repository and provides syntax highlighting, diagnostics and the usual language features through home lsp. Any editor with a language-server client can be pointed at home lsp --stdio directly.

Edit this page on GitHub

Released under the MIT License.

Copyright © 2026 Home Programming Language