Rework error handling in mdbook-spec

This enhances mdbook-spec's error handling with multiple changes:

- Several errors are now conditionally warnings. This makes doing local
  development with `mdbook serve` much easier, as sometimes you are OK
  with temporarily having broken links. SPEC_DENY_WARNINGS still rejects
  these.
- Collect multiple errors, and display all of them, instead of bailing
  on the very first error.
- Show a count of the number of warnings or errors.

This is done by introducing a new `Diagnostics` struct for emitting
warnings and errors. The `warn_or_err!` macro provide the primary
interface for emitting warnings.

I also added a `bug!` macro for internal errors that will immediately
exit. This is slightly nicer output than using `panic!`.
3 files changed
tree: 8b5312d96496db902685d3195a5a31b9260cf9b2
  1. .github/
  2. docs/
  3. mdbook-spec/
  4. src/
  5. style-check/
  6. theme/
  7. .gitattributes
  8. .gitignore
  9. book.toml
  10. CONTRIBUTING.md
  11. LICENSE-APACHE
  12. LICENSE-MIT
  13. README.md
  14. reference.md
  15. rust-toolchain.toml
  16. STYLE.md
  17. triagebot.toml
README.md

The Rust Language Reference

This document is the primary reference for the Rust programming language.

This document is not normative. It may include details that are specific to rustc itself, and should not be taken as a specification for the Rust language. We intend to produce such a document someday, but this is what we have for now.

Dependencies

Installing dependencies

First, ensure that you have a recent copy of the nightly Rust compiler installed, as this is needed in order to run the tests:

rustup toolchain install nightly

Now, ensure you have mdbook installed, as this is needed in order to build the Reference:

cargo install --locked mdbook

Building

To build the Reference, first clone the project:

git clone https://github.com/rust-lang/reference.git

(Alternatively, if you don't want to use git, download a ZIP file of the project, extract it using your preferred tool, and rename the top-level directory to reference.)

Now change your current directory to the working directory:

cd reference

To test all of the code examples in the Reference, run:

mdbook test

For authors, consider using the server functionality which supports automatic reload.

To build the Reference locally (in build/) and open it in a web browser, run:

SPEC_RELATIVE=0 mdbook build --open

This will open a browser with a websocket live-link to automatically reload whenever the source is updated.

You can also use mdbook's live webserver option, which will automatically rebuild the book and reload your web browser whenever a source file is modified:

SPEC_RELATIVE=0 mdbook serve --open

SPEC_RELATIVE

The SPEC_RELATIVE=0 environment variable makes links to the standard library go to https://doc.rust-lang.org/ instead of being relative, which is useful when viewing locally since you normally don't have a copy of the standard library.

The published site at https://doc.rust-lang.org/reference/ (or local docs using rustup doc) does not set this, which means it will use relative links which supports offline viewing and links to the correct version (for example, links in https://doc.rust-lang.org/1.81.0/reference/ will stay within the 1.81.0 directory).

SPEC_DENY_WARNINGS

The SPEC_DENY_WARNINGS=1 environment variable will turn all warnings generated by mdbook-spec to errors. This is used in CI to ensure that there aren't any problems with the book content.

SPEC_RUST_ROOT

The SPEC_RUST_ROOT can be used to point to the directory of a checkout of https://github.com/rust-lang/rust. This is used by the test-linking feature so that it can find tests linked to reference rules. If this is not set, then the tests won't be linked.