This repository is for changing Rust, not installing it
The rust-lang/rust repository contains the compiler, standard library, and documentation. Rust targets native software where speed and control matter, while its type system and ownership rules catch many memory and thread-safety mistakes before a program runs. This source tree is a poor way to get rustc onto a laptop. The README sends new users to the normal installation path and warns that source installation is not recommended.
Our commit 8d1a764 checkout held 424,963 files, about 35,716,967 lines of source, and occupied 3,498.7 MB. Those figures arrive before a compiler build creates its own output. The tree includes tests, documentation, bootstrap code, platform support, and imported components. A developer evaluating the language should start with the installer and The Book. A developer changing name resolution or a standard-library API belongs here.
The 24-second Yarn install did not build Rust
Our lab detected a Node and Yarn layer and installed 138 packages in 24 seconds, adding 70 MB on disk. The root automation exposed no build script or target and no test script or target, so the lab skipped both steps. That result covers auxiliary JavaScript tooling only. It is not a compiler build, a standard-library build, or a passing Rust test suite.
Package installation can be green while the product's real build path remains untouched. Rust's documented workflow runs through x.py, a Python script at the repository root that manages the staged bootstrap. Configuration lives in bootstrap.toml, with an interactive x.py setup for choosing a profile and development settings. Yarn is incidental to that path.
What happened when we ran it
We ran commit 8d1a764 in an unprivileged container with 3 CPUs, 8 GB of RAM, Node 22, and no secrets. The 138-package Yarn install finished in 24 seconds and used 70 MB. No build script or target existed, so build was skipped. No test script or target existed either, so tests were skipped. Our run produced no compiler build time, Rust test count, or compiler pass or failure result.
The scan found 3 CI workflow files, no Dockerfile, and a tests directory. Tests exist even though the detected package workflow could not invoke them. The checkout measured 3,498.7 MB across 424,963 files. The 70 MB dependency addition belongs to the Yarn utility layer; the multi-gigabyte tree is the language implementation.
x.py owns the compiler build
On Unix, the source guide requires Python, Git, a C compiler, curl, and pkg-config. Building Cargo also needs OpenSSL. Building LLVM locally adds a C++ compiler, CMake, and Ninja or GNU Make. The guide recommends Ninja, especially on Windows. A compiler contributor is maintaining a native toolchain, even though Python launches the top-level command.
The default route starts with x.py setup, then uses x.py build; installation is separate. Configuration can select the host, targets, tools, sanitizers, documentation, and LLVM behavior. Windows adds MSVC and GNU ABI paths, with Visual Studio 2022 or later named for actively tested MSVC builds. One generic container cannot represent every supported contributor path.
Bootstrapping requires a compiler snapshot and network access
Rust is written in Rust, so a source build needs an earlier precompiled compiler to create the next one. The install guide calls this a snapshot and says source builds require internet access to fetch it. The host must be able to execute an available snapshot binary. Only platforms with host tools receive that starting point; other targets need cross-compilation.
A mirrored source repository alone is insufficient for a clean offline build unless you also arrange the snapshot and other fetched material. LLVM adds another choice: eligible Tier 1 and Tier 2 host-tools platforms can download a CI build, while other setups need a system LLVM or a local build. Reproducibility begins with those inputs, not with the 138 Yarn packages our sandbox installed.
October 2026 activity shows a busy compiler project
GitHub showed 119,699 stars and a last push on October 8, 2026. Rust 1.99.0 was released on October 1 with language, compiler, library, Cargo, rustdoc, and platform changes. Issue searches returned 11,241 open issues and 1,417 open pull requests during our check. Those counts cover a language, compiler, standard library, and multi-platform project. The same-month push and release show active maintenance.
The contribution guide points newcomers to the rustc development guide and a dedicated Zulip stream. Changes to submodules and subtrees may belong in their own repositories. There is also a written policy for LLM use in contributions. These rules answer questions that appear when a change crosses compiler teams, imported components, or automated review.
Use the installer for Rust and this tree for rustc
Evaluate Rust by writing a real program, testing Cargo, studying ownership, and checking target support. None of those steps requires a 3,498.7 MB source checkout. The regular installer gives application developers the maintained compiler and tools without asking them to bootstrap the compiler that built them.
Clone this repository for compiler patches, standard-library work, implementation-linked documentation, or downstream distribution. Then treat x.py, snapshots, native compilers, and LLVM as the setup. Our lab's 24-second Yarn success exposes a trap in automated reviews: a package manager can finish perfectly while the actual product remains unbuilt and untested.