TorbScript

TorbScript is a programming language for scripts, tools and servers. Its command is torb and its files end in .trb. It is statically typed, with value semantics: a second name is a copy, and every change is marked. There is no null and no exception: a value that may be missing or a call that may fail says so in its type. torb run starts a program at once, and torb build turns the same program into a fast native one.

Learn#

• TorbScript in 10 ideas - the shape of the language in five minutes.
• A tour of TorbScript - the whole language in fifteen minutes, every example runs in the page.
• Learn TorbScript - one short page per idea, done in an evening.
• Learn to program - from zero, in short lessons you do in the browser.

Look up#

• Syntax cheat sheet - every form of the language on one page.
• The standard library - every package of std, grouped by what it is for.
• Errors - Option, Result, ? and what a panic is for.
• Tasks - Task, await() and spawn.
• The torb command - run, build, test, format and publish.
• Glossary - every term, one entry each.

Sections#

• Learn to program - A course for people who have never written a program, in thirteen short lessons you do in the browser, each with one idea and one small exercise.
• Learn TorbScript - For people who already program - a fifteen-minute tour, then one short page per idea, all of it done in an evening.
• The language reference - One page per construct of TorbScript, grouped by area, with the exact rules and the mistakes each construct invites.
• The standard library - One page per package of std, what each contains, and which of them are in scope everywhere without an import.
• Task recipes - One page per task for somebody who already knows the language: the steps, the pitfalls, and one complete program that works.
• Why the language is like this - The arguments behind the decisions, and the contrast pages for people and models arriving from Rust, Swift, Kotlin or TypeScript.
• The toolchain - The torb command, the project files, and how to verify that what you wrote is correct and in the formatter canon.

Pages#

• Glossary - Every term this documentation uses, one entry each, at most two sentences. The entry decides which word is correct.