These pages may contain out-of-date information. We hope to update or replace this information in the future.
Tips and tricks for developers just starting to work with the Mercury source code.
Outlines the main parts of the Mercury implementation, shows what directories contain each component, and the rationale behind this design.
Outlines the overall structure of the compiler, and explains how each module fits into it.
The code style standard we use for Mercury code in the Mercury implementation.
The code style standard we use for C code in the Mercury implementation. The runtime system of Mercury is written in C, and so are some of the lowest-level parts of the Mercury standard library.
The procedure we use to review proposed changes, including what should be done to prepare for reviews.
What to do when a change requires bootstrapping.
Explanations of some terms used in the Mercury implementation.
Features on which work has begun but has stopped short of completion.
These documents, plus more specific, incomplete and sometimes outdated
documents are kept in the compiler/notes/ directory of the
source tree.
They are also available online.