Version: 5.2.1

Unstable: May Change Without Warning

This manual documents some of the libraries available in the unstable collection.

The name unstable is intended as a warning that the interfaces in particular are unstable. Developers of planet packages and external projects should avoid using modules in the unstable collection. Contracts may change, names may change or disappear, even entire modules may move or disappear without warning to the outside world.

Developers of unstable libraries must follow the guidelines in Guidelines for Developing unstable Libraries.

    1 Guidelines for Developing unstable Libraries

    2 Automata: Compiling State Machines

    3 Bytes

    4 Contracts

    5 Contracts for Macro Subexpressions

    6 Debugging

    7 Definitions

    8 Filesystem

    9 Find

    10 Futures

    11 Functions

    12 Generics

    13 Hash Tables

    14 Interface-Oriented Programming for Classes

    15 Lazy Require

    16 Lists

    17 Logging

    18 Mark Parameters

    19 Match

    20 Parameter Groups

    21 Ports

    22 Pretty-Printing

    23 Sequences

    24 Strings

    25 Structs

    26 Syntax

    27 Temporal Contracts: Explicit Contract Monitors

    28 GUI Libraries