LLM Policy for Rust Compiler

Hacker News Top Tools

Summary

This article describes the Rust Forge, a repository of supplementary documentation for the Rust programming language, with instructions for building, contributing, and maintaining the documentation.

No content available
Original Article
View Cached Full Text

Cached at: 05/15/26, 03:28 AM

rust-lang/rust-forge

Source: https://github.com/rust-lang/rust-forge

Rust Forge

Welcome to the Rust Forge! Rust Forge serves as a repository of supplementary documentation useful for members of The Rust Programming Language.

Development

You can build a local version by installing mdbook and running the following command.

mdbook build

This will build and run the blacksmith tool automatically. When developing it’s recommended to use the serve command to launch a local server to allow you to easily see and update changes you make.

mdbook serve

Link checking

On CI, we automatically check if all intra-doc links in the Forge Markdown files are valid. If you would like to perform this check locally, install mdbook-linkcheck2 using cargo install [email protected] --locked and then simply run mdbook build or mdbook serve.

Blacksmith

Blacksmith is a tool that can run before the Forge is built. It downloads information about Rust releases, which is used to render a page with historical Rust releases.

Since it takes a while to compile and run, it is disabled by default. To enable it, run mdbook serve or mdbook build with the environment variable RUN_BLACKSMITH=1.

JavaScript

Forge uses JavaScript to display dates for releases and “no tools breakage week”. When making modifications to the JavaScript, make sure it matches the standard style. You can install standard and automatically format the code using the following commands.

Install commands

# With Yarn
yarn global add standard
# With NPM
npm install --global standard

Formatting

standard --fix js/

Contributing

Adding teams

Any Rust team, working group, or project group can have a section in the Rust Forge. First, please send a PR to add your team to the repos/rust-lang/rust-forge.toml file to give your team permissions.

To add your team to the book, add it to src/SUMMARY.md, like below, replacing <TEAM_NAME> with a filesystem- and URL-friendly version of your team’s name:

- [<TEAM NAME>](src/<TEAM_NAME>/index.md)

If you run mdbook build, mdbook will automatically create the folder and file for your team.

It’s recommended that you put general team information in src/<TEAM_NAME>/index.md, such as where the meetings happen, repositories that the team manages, links to chat platforms, etc. Larger topics should be made as a subpage, e.g. (src/release/topic.md).

- [TOPIC](src/<TEAM_NAME>/TOPIC.md)

Teams are responsible for merging their own content. Please add your team to the [assign.owners] section of triagebot.toml so that the bot will auto-assign someone from the team.

Maintenance of Rust Forge

The Rust infra team is responsible for maintaining the Rust Forge, ensuring that its build and publish system works, and coordinating any technical issues with teams.

Similar Articles

Bun's problem may be developing in the open

Lobsters Hottest

An article analyzing the controversy around Bun's experimental use of an LLM to transpile its Zig codebase to Rust, emphasizing that the public uproar stemmed from transparent development practices rather than the experiment itself.

Performance of Rust language

Lobsters Hottest

This talk analyzes Rust's performance strengths and weaknesses compared to C++, providing benchmarks and best practices. Slides and reading materials are available.

Building ML framework with Rust and Category Theory

Hacker News Top

This article announces a working draft book 'Category Theory for Tiny ML in Rust' and a public workshop introducing a tiny ML pipeline using Rust and category theory, aimed at making machine learning structure explicit through typed transformations.

What would you want from a forge?

Lobsters Hottest

A discussion thread on Lobsters asking developers what features they would like to see in a code forge, particularly regarding version control presentation and collaboration models, referencing tools like Jujutsu and Git.