A general-purpose, ahead-of-time compiled language with algebraic effects
English | 简体中文
Work in Progress :) Not Ready!
https://shd101wyy.github.io/Yo
A multi-paradigm, general-purpose, compiled programming language. Yo aims to be Simple and Fast (around 0% - 15% slower than C).
The name
Yocomes from the Chinese word柚(yòu), meaningpomelo, a large citrus fruit similar to grapefruit. It's my daughter's nickname.
📖 My Story with Programming Languages — the journey from Java at 16 to building Yo.
For the design of the language, please refer to DESIGN.md.
Below is a non-exhaustive list of features that Yo supports:
using/given, effect handlers with return/escape, by Evidence Passing).IO effect. Stackless coroutine & Cooperative multi-tasking. Lazy Futures, multi-await, single-threaded concurrency via state machine transformation).object type with Non-atomic Reference Counting and Thread-Local Cycle Collection.yo build, yo init, WASM targets).The Yo language is currently distributed as an npm package:
$ npm install -g @shd101wyy/yo # Install yo compiler globally
$ yarn global add @shd101wyy/yo # Or using yarn
$ pnpm add -g @shd101wyy/yo # Or using pnpm
$ bun install --global @shd101wyy/yo # Or using bun
It exposes the yo command in your terminal.
There is also an alias yo-cli for yo command in case of naming conflicts.
Run yo --help or yo-cli --help to see available commands.
Yo transpiles to C, so a C compiler is required to produce machine code. Follow the instructions for your platform below.
Install Clang (recommended), liburing (for async I/O), and pkg-config (for system library discovery):
# Ubuntu/Debian
$ sudo apt-get update
$ sudo apt-get install clang liburing-dev pkg-config
# Fedora/RHEL
$ sudo dnf install clang liburing-devel pkgconf-pkg-config
# Arch Linux
$ sudo pacman -S clang liburing pkgconf
You can also use gcc or zig instead of clang by passing --cc gcc or --cc zig.
Clang is included with Xcode Command Line Tools:
$ xcode-select --install
# Also install pkgconf for system library discovery
$ brew install pkgconf
Or install LLVM via Homebrew:
$ brew install llvm pkgconf
Clang on Windows requires a linker and Windows SDK headers. Install Visual Studio (Community edition is free) or the Build Tools for Visual Studio with the "Desktop development with C++" workload:
# Using Chocolatey
$ choco install llvm
# Using Scoop
$ scoop install llvm
# Or download from https://releases.llvm.org/
Alternatively, you can use zig as the C compiler (no Visual Studio needed):
$ choco install zig
$ yo compile main.yo --cc zig --release -o main
For system library discovery, install vcpkg:
$ git clone https://github.com/microsoft/vcpkg.git
$ .\vcpkg\bootstrap-vcpkg.bat
# Then set the VCPKG_ROOT environment variable to the vcpkg directory
# Or using Scoop
$ scoop install vcpkg
For more information, see the vcpkg documentation.
Yo can compile to WebAssembly using Emscripten:
# Install Emscripten (https://emscripten.org/docs/getting_started/downloads.html)
$ git clone https://github.com/emscripten-core/emsdk.git
$ cd emsdk
$ ./emsdk install latest
$ ./emsdk activate latest
$ source ./emsdk_env.sh
# Compile a Yo program to WASM
$ yo compile main.yo --cc emcc --release -o app
# This produces: app.html + app.js + app.wasm
# Run with Node.js:
$ node app.js
# Or open app.html in a browser
When using --cc emcc, Yo automatically targets wasm32-emscripten and uses the libc allocator. You can also use --target wasm-emscripten (which auto-selects emcc). Emscripten produces an .html file (browser shell), a .js file (runtime glue), and a .wasm file (compiled binary).
$ yo init my-project # Scaffold a new project
$ cd my-project
$ yo build run # Build and run
Hello, world!
yo init generates a project with a build file, source, and tests:
my-project/
├── build.yo # Build configuration
├── src/
│ ├── main.yo # Entry point
│ └── lib.yo # Library module
└── tests/
└── main.test.yo # Unit tests
src/main.yo:
{ println } :: import "std/fmt";
main :: (fn() -> unit)({
println("Hello, world!");
});
export main;
Common build commands:
$ yo build # Build all artifacts
$ yo build run # Build and run the executable
$ yo build test # Run tests
$ yo build --list-steps # List available build steps
$ yo build doc # Generate HTML documentation
Every Yo file automatically imports std/prelude.yo, which provides the core types, traits, and builtins available without any explicit import:
bool, i8–i64, u8–u64, f32, f64, isize, usize, strint, uint, short, long, longlong, char, etc.Eq, Ord, Add, Sub, Mul, Div, Iterator, IntoIterator, TryFrom, TryInto, Dispose, Send, Rc, Acyclic, etc.Type, Expr, ExprList, VarIO, FutureState, JoinHandleassert, unsafe, try, for, not, arc, Box, boxStill In Design
Yo ships with a comprehensive standard library covering strings, collections, file I/O, networking, encoding, regex, crypto, and more. For the full module reference, see the Standard Library Documentation.
You can generate documentation for your own project with yo doc:
$ yo doc ./src -o docs --title "My Project"
Or add a documentation step to your build.yo — see yo doc --help for details.
Check the ./tests and ./std folders for more code examples.
// main.yo
{ println } :: import "std/fmt";
main :: (fn() -> unit) {
println("Hello, world!");
};
export main;
// $ yo compile main.yo --release -o main
// $ ./main
| Project | Description |
|---|---|
| raylib_yo | Comprehensive raylib bindings — 35 struct types, 535 functions, 227 constants |
| tetris_yo | Online Demo | Classic Tetris game built with raylib_yo, demonstrating Yo's build system and C interop |
| http_server_demo_yo | Simple HTTP/1.1 server — async I/O, algebraic effects, TCP networking, request parsing & routing |
| markdown_it_yo | Direct port of the popular JavaScript markdown parser markdown-it to Yo, showcasing string processing and performance |
| markdown_yo | Online Demo | High-performance markdown-to-HTML converter — 5-7× faster than markdown-it (native), 2-6× faster (WASM at ≥1 MB). Try it in the browser |
| yo_http_benchmark | HTTP throughput benchmark — Yo vs Bun vs Deno vs Node.js vs Go, using wrk load testing |
The Yo compiler is written in TypeScript and uses Bun as the runtime.
Yo is primarily developed on the Steam Deck LCD (Linux). The compiler currently transpiles Yo to C; to produce
machine code you must have a C compiler (for example gcc, clang, zig, cl, emcc, etc).
Please install nix and direnv before proceeding.
The dev environment is defined in shell.nix. You can also manually install the dependencies listed in the file.
$ cd Yo
$ direnv allow . # Run this command to activate the nix shell.
# You only need to run it once.
$ bun install # Install necessary dependencies.
Run the following command to watch for changes and build the project:
$ bun run dev
Run the following command to build the project:
$ bun run build
Test the local yo-cli:
$ bun run src/yo-cli.ts compile src/tests/examples/fixme.yo
# There is also a `yo-cli` script in the project root for testing:
$ ./yo-cli compile src/tests/examples/fixme.yo
A VS Code extension is available here with built-in Language Server Protocol (LSP) support, providing:
The LSP server can also be used with other editors via stdio JSON-RPC:
node out/cjs/yo-lsp.cjs --stdio
See docs/en-US/LSP.md for full documentation.
Vim / Neovim: a minimal syntax file and a usage README are available in vscode-extension/syntaxes/.
See vscode-extension/syntaxes/README.md for installation steps, ftdetect examples and home-manager snippets.
Yo supports per-project version pinning via a .yo-version file (similar to .nvmrc or .python-version):
# Pin your project to a specific Yo version
yo version pin 0.1.12
# Show current and pinned version
yo version
# Install, list, and clean cached versions
yo version install 0.1.13
yo version list
yo version clean
When a .yo-version file exists, the yo CLI automatically dispatches to the pinned version — downloading and caching it on first use. The LSP server also reads .yo-version to resolve the correct standard library for go-to-definition and completions.
See docs/en-US/VERSION_MANAGEMENT.md for full documentation.
This repository ships a set of agent skill files that teach AI agents how to write Yo programs. The skills are portable — you can copy the .github/skills/ directory into any Yo project and agents will be able to use them there too.
| Skill | Description |
|---|---|
yo-syntax |
Core language syntax: curly braces, cond/match, structs, enums, operators, modules |
yo-core-patterns |
Everyday patterns: types, generics, traits, error handling, collections, iterators |
yo-async-effects |
Async/await, algebraic effects, Exception, IO, spawning tasks |
yo-project-workflow |
yo CLI commands, build.yo project files, dependency management |
The easiest way is with the yo CLI:
yo skills install
This copies all skill files into every agent config directory found in the current project (.github, .agents, .claude, .opencode, .openai, .cursor). If none exist, .agents/skills/ is created automatically.
You can also copy them manually:
cp -r .github/skills /path/to/your-yo-project/.github/
# or .agents, .claude, etc depending on your agent platform
Then in any AI agent session, invoke a skill by name (e.g. @yo-syntax) to give the agent contextual knowledge about the Yo language.