7 Units

► |  | The Racket Reference

1 | Language Model
2 | Notation for Documentation
3 | Syntactic Forms
4 | Datatypes
5 | Structures
6 | Classes and Objects
7 | Units
8 | Contracts
9 | Pattern Matching
10 | Control Flow
11 | Concurrency and Parallelism
12 | Macros
13 | Input and Output
14 | Reflection and Security
15 | Operating System
16 | Memory Management
17 | Unsafe Operations
18 | Running Racket
| Bibliography
| Index

▼ | 7 | Units

7.1 | Creating Units
7.2 | Invoking Units
7.3 | Linking Units and Creating Compound Units
7.4 | Inferred Linking
7.5 | Generating A Unit from Context
7.6 | Structural Matching
7.7 | Extending the Syntax of Signatures
7.8 | Unit Utilities
7.9 | Unit Contracts
7.10 | Single-Unit Modules
7.11 | Single-Signature Modules
7.12 | Transformer Helpers

top contents ← prev up next →

### 7`` Units🔗ℹ

> > > Units in The Racket Guide introduces units.

Units organize a program into separately compilable and reusable components. The imports and exports of a unit are grouped into a signature, which can include “static” information (such as macros) in addition to placeholders for run-time values. Units with suitably matching signatures can be linked together to form a larger unit, and a unit with no imports can be invoked to execute its body.

(require racket/unit) | package: base

The bindings documented in this section are provided by the racket/unit and racket libraries, but not racket/base. The racket/unit module name can be used as a language name with #lang; see Single-Unit Modules.

7.1 Creating Units
7.2 Invoking Units
7.3 Linking Units and Creating Compound Units
7.4 Inferred Linking
7.5 Generating A Unit from Context
7.6 Structural Matching
7.7 Extending the Syntax of Signatures
7.8 Unit Utilities
7.9 Unit Contracts
7.10 Single-Unit Modules
7.11 Single-Signature Modules
7.12 Transformer Helpers

top contents ← prev up next →