Lexical basics

Before types, the lexer decides whether your file is even language or performance art.

Surface shape (informative)

Beskid source uses familiar C-family cues:

• Identifiers and keywords
• Braces and semicolons where the grammar demands
• Line and block comments (//, /* */ per spec)
• String and numeric literals (exact lexical rules: lexical and syntax)

Modules still matter lexically

File-scoped mod must appear as the first top-level item when used. The parser assumes structure before semantic phases attach module identity.

Documentation comments

/// doc comments attach to declarations; @arg belongs on callable parameters only—not fields you felt like documenting. Tutorial on docs arrives later; normative: documentation comments.

Escape hatch

When the lexer/parser disagrees with you, shrink to a five-line file and run:

beskid parse tiny.bd
beskid tree tiny.bd

flowchart LR
  SRC[.bd file] --> LEX[lexical]
  LEX --> PAR[parse]
  PAR --> SEM[semantic]

Next

Types and generics