Version: 5.3.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 Converting Values to Strings

    6 Contracts for Macro Subexpressions

    7 Debugging

    8 Definitions

    9 Errors

    10 Filesystem

    11 Find

    12 Flonums

    13 Futures

    14 Functions

    15 Hash Tables

    16 Interface-Oriented Programming for Classes

    17 Lazy Require

    18 Lists

    19 Logging

    20 Mark Parameters

    21 Match

    22 Open place expressions

    23 Parameter Groups

    24 Pretty-Printing

    25 Re-Contracting Identifiers

    26 Sandbox

    27 Sequences

    28 Strings

    29 Structs

    30 Struct Printing

    31 Syntax

    32 Temporal Contracts: Explicit Contract Monitors

    33 GUI Libraries