Version: 5.2

Unstable: May Change Without Warning

 (require unstable)

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 Contracts for struct type properties

    7 Debugging

    8 Definitions

    9 Dictionaries

    10 Exceptions

    11 Filesystem

    12 Find

    13 Futures

    14 Finding Mutated Variables

    15 Functions

    16 Generics

    17 Hash Tables

    18 Interface-Oriented Programming for Classes

    19 Lazy Require

    20 Lists

    21 Logging

    22 Mark Parameters

    23 Match

    24 Net

    25 Path

    26 Ports

    27 Pretty-Printing

    28 Requiring Modules

    29 Sequences

    30 Strings

    31 Structs

    32 Syntax

    33 Temporal Contracts: Explicit Contract Monitors

    34 GUI libraries