Keyword `set`

set is documented here as a full reference entry: grammatical role, semantics, canonical form, valid example, counter-example, diagnostics, interactions, and design notes.

Visual anchor: each page now has its own wiki-style profile image. It shows a small code excerpt where set appears in its most recognizable form.

Quick navigation: use the previous, summary, and next links to move through the full keyword series without manually returning to the index.

Summary

Overview
Definition
Grammatical role
Canonical syntax
Detailed semantics
Effect on execution
Valid variants
Vitte example
Guided reading of the example
Comparison with C
Recommended uses
Invalid example and diagnostic
Common errors
Neighbor keywords
Common misreadings
Implementation notes
Presence in the book

Overview

Field	Value
Keyword	`set`
Family	Binding and mutation
Suggested level	Beginner
Main neighbor	`let`
Short role	`set` is a binding or assignment keyword that changes how local state is introduced or updated.
Main effect	`set` acts on the program's local state by introducing or modifying a named value that subsequent instructions will read.

The keyword set acts on the visible state of a block. It introduces, initializes, or modifies a value, which makes it a critical point for invariant readability.

A useful encyclopedic reading should answer three questions: where can set appear, what does it change in the block contract, and how does the compiler signal misuse?

Definition

set is a binding or assignment keyword that changes how local state is introduced or updated.

The keyword set acts on the visible state of a block. It introduces, initializes, or modifies a value, which makes it a critical point for invariant readability.

Grammatical role

Updates an already existing binding.

This grammatical role is essential: if a reader understands the structural place of set, they already understand much of the diagnostics that will appear when it is moved or truncated.

Canonical syntax

Canonical form: `set name = value`.

The canonical form matters because it gives the compiler and the reader the same reference structure. A large share of diagnostics related to set come from an abbreviated, displaced, or incomplete form.

Detailed semantics

Semantically, set evolves the state of a local name. It should therefore be read together with scope, lifetime, and the distinction between introducing a value and updating an existing one.

In an encyclopedic reading, set should not be reduced to a dictionary definition. Its effect on scope, block shape, value visibility, control progression, and the diagnostic family it activates when misused must also be considered.

Effect on execution

set acts on the program's local state by introducing or modifying a named value that subsequent instructions will read.

In other words, the presence of set is not merely syntactic: it helps the reader predict what will be executed, produced, exposed, or forbidden from this point in the program.

Valid variants

`set name = value`

These variants are not free synonyms. They indicate the legitimate forms from which one can reason about diagnostics, scope differences, or contract readability.

Vitte example

proc bump() -> int {
  let value: int = 1
  set value = value + 1
  give value
}

This example shows set in a nominal context. It should be read globally: where the contract begins, which values are constrained, which output becomes observable, and why the presence of the keyword is justified.

Guided reading of the example

First locate the full construction that contains set, not the isolated word.
Then identify which contract becomes visible because of set: type, branch, binding, module, exit, or advanced boundary.
Finish by checking the observable effect produced by the construction that contains set.
For a binding keyword, distinguish name introduction, mutation, and value scope.

This guided reading is intentionally closer to a reference page than to a tutorial: it helps reconstruct the exact role of set in a complete block.

Comparison with C

/* C comparison: declarations and assignments are usually split across local variables and direct assignment. */

For this keyword, the parallel with C remains approximate. The comparison mainly indicates that in C the same idea is often spread across file conventions, operators, or less explicit control structures.

The source of truth remains Vitte grammar and semantics. The comparison with C should be read as a cultural marker, not as a parallel specification.

Recommended uses

set deserves to appear when it simplifies the reading of the block's global contract, not when it merely adds one more surface form.

When to use it

When set makes the block contract more explicit at first reading.
When it reduces the number of implicit assumptions the reader must reconstruct mentally.
When local state must be introduced or modified without ambiguity about the name's scope.

When to avoid it

Avoid set when another, more precise keyword already carries the block's intent.
Avoid set when it adds only surface noise without clarifying the contract.
Avoid reading or teaching it as an isolated token with no relation to the full structure.

Common pitfalls

Using set in a grammatical layer where it does not belong.
Confusing the role of the keyword with the role of the full surrounding block.
Showing only the nominal form and never how the contract fails.

Invalid example and diagnostic

proc bad_set() -> int {
  set
  give 0
}

The binding surface is incomplete or appears in the wrong form.

The counter-example is not merely wrong: it is wrong in an instructive way. It shows which grammar or execution-contract assumption is no longer accepted when set is moved, truncated, or combined with the wrong context. Concretely, the mutation targets a binding or assignment form that is incomplete.

A good encyclopedic counter-example does not show arbitrarily broken code: it isolates the precise reason why set can no longer support the expected contract. Its teaching value is diagnostic before it is syntactic.

Common compilation errors

Typical message	Usual cause	Fix
`unexpected token near set`	The keyword appears in an invalid form or grammatical layer.	Return to the canonical form and verify placement and delimiters.
`type mismatch`	The keyword participates in a block whose value contract is incoherent.	Realign the surrounding types, branches, or produced values.
`invalid construct`	The keyword is present but the surrounding construction is incomplete.	Restore the missing branch, declarative part, or operands.

This table does not replace the compiler's exact diagnostics. It serves as a mental map: when set fails, the problem usually comes from an invalid grammatical form, an incoherent type contract, or an incomplete construction.

Neighbor keywords

Keyword	Operational difference
`let`	Direct neighboring keyword: it helps explain what `set` does, either by contrast or by complement.

Comparison with neighboring keywords is essential on a wiki-style page: set is better understood when one knows precisely what it does not do.

Common misreadings

Reducing set to a local token instead of reading it as part of a full construction.
Explaining only the syntax and forgetting the reading or diagnostic contract it imposes.

Implementation and diagnostic notes

Common errors concern scope, illegal reassignment, or an incompatible type contract between introduction and use.
In a compiler, these keywords modify the local environment and mutability or assignment information.

Keyword set