Rust (programming language)

Rust

The official Rust logo
Paradigms	Multi-paradigm: concurrent, functional, generic, imperative, structured
Designed by	Graydon Hoare
First appeared	July 7, 2010 (2010-07-07)
Stable release	1.82.0  / October 17, 2024 (October 17, 2024)
Typing discipline	Affine, inferred, nominal, static, strong
Implementation language	Rust
Platform	Cross-platform
OS	Cross-platform
License	MIT and Apache 2.0 (dual-licensed)
Filename extensions	.rs, .rlib
Website	www.rust-lang.org
Influenced by
Alef C# C++ Cyclone Erlang Haskell Limbo Newsqueak OCaml Ruby Scheme Standard ML Swift
Influenced
Carbon Crystal Idris Spark Swift Project Verona Zig

Rust is a multi-paradigm, general-purpose programming language. Rust emphasizes performance, type safety, and concurrency. Rust enforces memory safety—that is, that all references point to valid memory—without requiring the use of a garbage collector or reference counting present in other memory-safe languages. To simultaneously enforce memory safety and prevent concurrent data races, Rust's borrow checker tracks the object lifetime and variable scope of all references in a program during compilation. Rust is popular for systems programming but also offers high-level features including functional programming constructs.

Software developer Graydon Hoare designed Rust while working at Mozilla Research in 2006. Mozilla officially sponsored the project in 2009, and the designers refined the language while writing the Servo experimental browser engine and the Rust compiler. Rust's major influences include SML, OCaml, C++, Cyclone, Haskell, and Erlang. Since the first stable release in January 2014, Rust has been adopted by companies including Amazon, Discord, Dropbox, Facebook (Meta), Google (Alphabet), and Microsoft.

Rust has been noted for its growth as a newer language and has been the subject of academic programming languages research.

History

Origins (2006–2012)

Mozilla Foundation headquarters in Mountain View, California

Rust grew out of a personal project begun in 2006 by Mozilla employee Graydon Hoare. Mozilla began sponsoring the project in 2009 and officially announced the project in 2010. During the same year, work had shifted from the initial compiler written in OCaml to a self-hosting compiler based on LLVM written in Rust. The new Rust compiler, named rustc, successfully compiled itself in 2011. The first numbered pre-alpha version of the compiler, Rust 0.1, was released in January 2012.

Evolution (2013–2019)

Rust's type system changed considerably between versions 0.2, 0.3, and 0.4. Version 0.2 introduced classes for the first time, and version 0.3 added destructors and polymorphism through the use of interfaces. In Rust 0.4, traits were added as a means to provide inheritance; interfaces were unified with traits and removed as a separate feature. Classes were also removed and replaced by a combination of implementations and structured types. Along with conventional static typing, before version 0.4, Rust also supported typestate analysis through contracts. It was removed in release 0.4, though the same functionality can be achieved by leveraging Rust's type system.

In January 2014, the editor-in-chief of Dr. Dobb's Journal, Andrew Binstock, commented on Rust's chances of becoming a competitor to C++ in addition to the languages D, Go, and Nim (then Nimrod). According to Binstock, while Rust was "widely viewed as a remarkably elegant language", adoption slowed because it repeatedly changed between versions. The first stable release, Rust 1.0, was announced on May 15, 2015.

Mozilla layoffs and Rust Foundation (2020–present)

In August 2020, Mozilla laid off 250 of its 1,000 employees worldwide as part of a corporate restructuring caused by the long-term impact of the COVID-19 pandemic. The team behind Servo, a browser engine written in Rust, was completely disbanded. The event raised concerns about the future of Rust, as some members of the team were active contributors to Rust. In the following week, the Rust Core Team acknowledged the severe impact of the layoffs and announced that plans for a Rust foundation were underway. The first goal of the foundation would be to take ownership of all trademarks and domain names, and take financial responsibility for their costs.

On February 8, 2021, the formation of the Rust Foundation was announced by its five founding companies (AWS, Huawei, Google, Microsoft, and Mozilla). In a blog post published on April 6, 2021, Google announced support for Rust within Android Open Source Project as an alternative to C/C++.

On November 22, 2021, the Moderation team, responsible for enforcing community standards and the Code of Conduct, announced their resignation "in protest of the Core Team placing themselves unaccountable to anyone but themselves." Although no further comments regarding the reasons for the resignation has been provided in the announcements, one of the former members of the Moderation team commented on Reddit, stating that "[c]ommunication with Core has failed, there's no team above Core, so... it's up to the members of the Rust Project to organize themselves and decide what to do in term of follow-up."

Syntax and semantics

Hello World program

Below is a "Hello, World!" program in Rust. The println! macro prints the message to standard output.

fn main() {
    println!("Hello, World!");
}

Keywords and control flow

In Rust, blocks of code are delimited by curly brackets, and control flow is annotated with keywords such as if, else, while, and for. Pattern matching is provided using the match keyword. In the examples below, explanations are given in comments, which start with //.

fn main() {
    let mut values = vec![1, 2, 3, 4];

    for value in &values {
        println!("value = {}", value);
    }

    if values.len() > 5 {
        println!("List is longer than five items");
    }

    // Pattern matching
    match values.len() {
        0 => println!("Empty"),
        1 => println!("One value"),
        2..=10 => println!("Between two and ten values"),
        11 => println!("Eleven values"),
        _ => println!("Many values"),
    };

    // while loop with predicate and pattern matching using let
    while let Some(value) = values.pop() {
        println!("value = {value}"); // using curly braces to format a local variable
    }
}

Expression blocks

Despite the syntactic resemblance to C and C++, Rust's design was more significantly influenced by functional programming languages. For example, nearly every part of a function body is an expression, even control flow operators. The ordinary if expression also takes the place of C's ternary conditional. A function does not need to end with a return expression: if the semicolon is omitted, the value of the last expression in the function will be used as the return value, as seen in the following recursive implementation of the factorial function:

fn factorial(i: u64) -> u64 {
    if i == 0 {
        1
    } else {
        i * factorial(i - 1)
    }
}

The following iterative implementation uses the ..= operator to create an inclusive range:

fn factorial(i: u64) -> u64 {
    (2..=i).product()
}

Types

Rust is strongly typed and statically typed, where all types of variables must be known during compilation, and assigning a value of a different type to a variable will result in a compilation error. The default integer type is i32, and the default floating point type is f64. The type of a literal is either specified as a suffix or inferred from the context.

Summary of Rust's built-in types

Type	Description	Examples
bool	Boolean value	true false
u8	Unsigned 8-bit integer (a byte)	1 (Inferred type) 255u8 (Explicit type) b'W' (ASCII encoded byte)
i8 i16 i32 i64 i128	Signed integers, up to 128 bits	7i128 (Explicit type) -42 (Inferred type)
u16 u32 u64 u128	Unsigned integers, up to 128 bits	14u128 (Explicit type) 0 (Inferred type)
usize isize	Pointer-sized integers (size depends on platform)	14usize (Explicit type) -2isize (Explicit type) 0 (Inferred type)
f32 f64	Floating-point numbers	-3f32 (Explicit type) 2.0 (Inferred type)
char	UTF-32 scalar value (occupies 4 bytes) A Unicode codepoint that is not a surrogate	'a' '语' '😂' (Emoji) '\u{200D}' (Unicode escape, Zero-width joiner)
&str	Strings (static or immutable)	"Hello" "3" "😂😂😂"
[T; N]	Static arrays (size known at compile-time)	[2, 4, 6] [0; 100] b"Hello"
[T]	Static arrays (size not known at compile-time)	[1, 2, 3, 4, 5][..i] "Hello, world!".as_bytes() let v = vec![1, 2, 3]; v.as_slice()
(T1, T2) (T1, T2, T3) ...	Tuples	() (An empty tuple, the unit type in Rust) (5,) (if this was (5), it would've been parsed as an integer) ("Age", 10) (1, true, "Name")
&T &mut T	References (immutable and mutable)	let x_ref = &x; let x_ref = &mut x;
*const T *mut T	Pointers (immutable and mutable) Possibly null; unsafe to dereference	let x_ptr = &x as *const T; let x_ptr = &mut x as *mut T;
!	Never type (unreachable value)	let x = { return 123 };

Unlike other languages, Rust does not use null pointers to indicate a lack of data, as doing so can lead to accidental dereferencing. Therefore, in order to uphold its safety guarantees, it is impossible to dereference null pointers unless the code block is manually checked and explicitly declared unsafe through the use of an unsafe block. Rust instead uses an Option type, which has two variants, Some(T) (which indicates that a value is present) and None (analogous to the null pointer). Option implements a "null pointer optimization" avoiding any overhead for types which cannot have a null value (references or the NonZero types for example). Option values must be handled using syntactic sugar such as the if let construction in order to access the inner value (in this case, a string):

fn main() {
    let name: Option<String> = None;
    // If name was not None, it would print here.
    if let Some(name) = name {
        println!("{}", name);
    }
}

Summary of Rust's types in the standard library

Type	Description	Examples
Box	A value in the heap	Box::new(5)
String	Strings (dynamic)	String::new() String::from("Hello") "😂😂😂".to_string()
Vec<T>	Dynamic arrays	Vec::new() vec![1, 2, 3, 4, 5]
Option<T>	Option type	None Some(3) Some("hello")
Option<&T> Option<&mut T>	Type-safe pointers Possibly null; safe to dereference	None let x_ref = Some(&x); let x_ref = Some(&mut x);
Result<T, E>	Error handling	Result::Ok(3) Result::Err("something went wrong")

Generics

More advanced features in Rust include the use of generic functions to achieve type polymorphism. The following is a Rust program to calculate the sum of two things, for which addition is implemented using a generic function:

use std::ops::Add;

// sum is a generic function with one type parameter, T
fn sum<T>(num1: T, num2: T) -> T
where   
    T: Add<Output = T>,  // T must implement the Add trait where addition returns another T
{
    num1 + num2  // num1 + num2 is syntactic sugar for num1.add(num2) provided by the Add trait
}

fn main() {
    let result1 = sum(10, 20);
    println!("Sum is: {}", result1); // Sum is: 30

    let result2 = sum(10.23, 20.45);
    println!("Sum is: {}", result2); // Sum is: 30.68
}

Generics in Rust use trait bounds for their generic parameters, which precisely define what is required of a type in order to be used with a given generic function. This allows generics in Rust to be type-checked at compile time, without having to know the exact types.

Ownership and lifetimes

Rust uses an ownership system, where each value has a unique owner. Values are moved between different owners through assignment or passing a value as a function parameter. Functions taking ownership of a parameter are said to consume the value in question. Ownership in Rust is similar to move semantics in C++; unlike C++, however, Rust keeps track of moved values and all types are movable by default. This means that types in Rust do not have to implement an "empty" or "invalid" state (and corresponding runtime checks) to signify that a value has been moved out of, because using a moved value is a compile-time error in Rust:

fn print_string(s: String) {
    println!("{}", s);
}

fn main() {
    let s = String::from("Hello, World");
    print_string(s);  // s consumed by print_string
    // s has been moved, so cannot be used any more
    // another print_string(s);  would result in a compile error
}

Lifetimes are a usually implicit part of all reference types in Rust. Each particular lifetime encompasses a set of locations in the code for which a variable is valid. The borrow checker in the Rust compiler uses lifetimes to ensure that the values pointed to by a reference remains valid. It also ensures that a mutable reference only exists if no immutable references exist at the same time.

Rust defines the relationship between the lifetimes of the objects used and created by functions as part of their signature using lifetime parameters. In languages like C or C++ the information about which objects have to outlive others is informally specified in documentation or comments, if at all, and cannot be checked by the compiler.

When a stack variable or temporary goes out of scope, it is dropped by running its destructor, which may be implicitly defined or a programmer-defined "drop" function. The latter can be used for design patterns akin to resource acquisition is initialization (RAII), in which resources, like file descriptors or network sockets, are tied to the lifetime of an object: When the object is dropped, the resource is closed.

The example below parses some configuration options from a string and creates a struct containing the options. The struct only contains references to the data, so for the struct to remain valid, the data referred to by the struct needs to be valid as well. The function signature for "parse_config" specifies this relationship explicitly. In this example, the explicit lifetimes are unnecessary in newer Rust versions due to lifetime elision, which is an algorithm that automatically assigns lifetimes to functions if they are trivial.

use std::collections::HashMap;

#[derive(Debug)]
// This struct has one lifetime parameter, 'src. The name is only used within the struct's definition.
struct Config<'src> {
    hostname: &'src str,
    username: &'src str,
}

// This function also has a lifetime parameter, 'cfg. 'cfg is attached to the "config" parameter, which
// establishes that the data in "config" lives at least as long as the 'cfg lifetime.
// The returned struct also uses 'cfg for it's lifetime, so it can live at most as long as 'cfg.
fn parse_config<'cfg>(config: &'cfg str) -> Config<'cfg> {
    let key_values: HashMap<_, _> = config
        .lines()
        .filter(|line| !line.starts_with('#'))
        .filter_map(|line| line.split_once('='))
        .map(|(key, value)| (key.trim(), value.trim()))
        .collect();
    Config {
        hostname: key_values["hostname"],
        username: key_values["username"],
    }
}

fn main() {
    let config = parse_config(
        r#"hostname = foobar
username=barfoo"#,
    );
    println!("Parsed config: {:#?}", config);
}

Features

A presentation on Rust by Emily Dunham from Mozilla's Rust team (linux.conf.au conference, Hobart, 2017)

Rust aims to support concurrent systems programming, which has inspired a feature set with an emphasis on safety, control of memory layout, and concurrency.

Memory safety

Rust is designed to be memory safe. It does not permit null pointers, dangling pointers, or data races. Data values can be initialized only through a fixed set of forms, all of which require their inputs to be already initialized. To replicate pointers being either valid or NULL, such as in linked list or binary tree data structures, the Rust core library provides an option type, which can be used to test whether a pointer has Some value or None. Rust has added syntax to manage lifetimes, which are checked at compile time by the borrow checker. Unsafe code can subvert some of these restrictions using the unsafe keyword. Unsafe code may also used for low-level functionality like volatile memory access, architecture-specific intrinsics, type punning, and inline assembly.

Memory management

Rust does not use automated garbage collection. Memory and other resources are managed through the resource acquisition is initialization convention, with optional reference counting. Rust provides deterministic management of resources, with very low overhead. Values are allocated on the stack by default and all dynamic allocations must be explicit.

The built-in reference types using the & symbol do not involve run-time reference counting. The safety and validity of the underlying pointers is verified at compile time, preventing dangling pointers and other forms of undefined behavior. Rust's type system separates shared, immutable references of the form &T from unique, mutable references of the form &mut T. A mutable reference can be coerced to an immutable reference, but not vice versa.

Types and polymorphism

Rust's type system supports a mechanism called traits, inspired by type classes in the Haskell language. Traits annotate types and are used to define shared behavior between different types. For example, floats and integers both implement the Add trait because they can both be added; and any type that can be printed out as a string implements the Display or Debug traits. This facility is known as ad hoc polymorphism.

Rust uses type inference for variables declared with the keyword let. Such variables do not require a value to be initially assigned to determine their type. A compile time error results if any branch of code leaves the variable without an assignment. Variables assigned multiple times must be marked with the keyword mut (short for mutable).

A function can be given generic parameters, which allows the same function to be applied to different types. Generic functions can constrain the generic type to implement a particular trait or traits; for example, an "add one" function might require the type to implement "Add". This means that a generic function can be type-checked as soon as it is defined. The implementation of Rust generics is similar to the typical implementation of C++ templates: a separate copy of the code is generated for each instantiation. This is called monomorphization and contrasts with the type erasure scheme typically used in Java and Haskell. Rust's type erasure is also available by using the keyword dyn (short for dynamic) .The benefit of monomorphization is optimized code for each specific use case; the drawback is increased compile time and size of the resulting binaries.

In Rust, user-defined types are created with the struct or enum keywords. The struct keyword denotes a record type. enums are kinds of algebraic data types commonly found in functional programming languages. These types can contain fields of other types. The impl keyword can define methods for the types (data and functions are defined separately) or implement a trait for the types. Traits are used to restrict generic parameters and because traits can provide a type with more methods than the user defined. For example, the trait Iterator requires that the next method be defined for the type. Once the next method is defined the trait provides common functional helper methods over the iterator like map or filter.

Type aliases, including generic arguments, can also be defined with the type keyword.

The type system within Rust is based around implementations, traits and structured types. Implementations fulfill a role similar to that of classes within other languages and are defined with the keyword impl. Traits provide inheritance and polymorphism; they allow methods to be defined and mixed in to implementations. Structured types are used to define fields. Implementations and traits cannot define fields themselves, and only traits can provide inheritance. Among other benefits, this prevents the diamond problem of multiple inheritance, as in C++. In other words, Rust supports interface inheritance but replaces implementation inheritance with composition; see composition over inheritance.

Trait objects

Rust traits are implemented using static dispatch, meaning that the type of all values is known at compile time; however, Rust also uses a feature known as trait objects to accomplish dynamic dispatch (also known as duck typing). Dynamically dispatched trait objects are declared using the syntax Box<dyn Tr> where Tr is a trait. For example, it is possible to create a list of objects which each can be printed out as follows: let v: Vec<Box<dyn Display>> = vec![Box::new(3), Box::new(5.0), Box::new("hi")]. Trait objects are dynamically sized; however, prior to 2015, the dyn keyword was optional. A trait object is essentially a fat pointer that include a pointer as well as additional information about what type the pointer is.

Macros

It is possible to extend the Rust language using macros.

Declarative macros

Declarative macros (also called "macros by example") are macros that uses pattern matching to determine its expansion.

Procedural macros

Procedural macros use Rust functions that are compiled before other components to run and modify the compiler's input token stream. They are generally more flexible than declarative macros, but are more difficult to maintain due to their complexity.

Procedural macros come in three flavors:

• Function-like macros custom!(...)
• Derive macros #[derive(CustomDerive)]
• Attribute macros #[custom_attribute]

The println! macro is an example of a function-like macro and serde_derive is a commonly used library for generating code for reading and writing data in many formats such as JSON. Attribute macros are commonly used for language bindings such as the extendr library for Rust bindings to R.

The following code shows the use of the Serialize, Deserialize and Debug derive procedural macros to implement JSON reading and writing as well as the ability to format a structure for debugging.

use serde_json::{Serialize, Deserialize};

#[derive(Serialize, Deserialize, Debug)]
struct Point {
    x: i32,
    y: i32,
}

fn main() {
    let point = Point { x: 1, y: 2 };

    let serialized = serde_json::to_string(&point).unwrap();
    println!("serialized = {}", serialized);

    let deserialized: Point = serde_json::from_str(&serialized).unwrap();
    println!("deserialized = {:?}", deserialized);
}

Interface with C and C++

Rust has a foreign function interface (FFI) that can be used both to call code written in languages such as C from Rust and to call Rust code from those languages. Rust also has a library, CXX, for calling to or from C++. Rust and C differ in how they lay out structs in memory, so Rust structs may be given a #[repr(C)] attribute, forcing the same layout as the equivalent C struct.

Components

Compiling a Rust program with Cargo

Besides the compiler and standard library, the Rust ecosystem includes additional components for software development. Component installation is typically managed by rustup, a Rust toolchain installer developed by the Rust project.

Standard library

The Rust standard library is split into three crates: core, alloc, and std. When a project is annotated with the crate-level attribute #![no_std], the std crate is excluded.

Cargo

Screenshot of crates.io in June 2022

Cargo is Rust's build system and package manager. Cargo downloads, compiles, distributes, and uploads packages, called crates, maintained in the official registry. Cargo also acts as a front-end for Clippy and other Rust components.

By default, Cargo sources its dependencies from the user-contributed registry crates.io, but Git repositories and crates in the local filesystem and other external sources can be specified as dependencies, too.

Rustfmt

Rustfmt is a code formatter for Rust. It takes Rust source code as input and changes the whitespace and indentation to produce code formatted in accordance to a common style unless specified otherwise. Rustfmt can be invoked as a standalone program or on a Rust project through Cargo.

Clippy

Example output of Clippy on a hello world Rust program

Clippy is Rust's built-in linting tool to improve the correctness, performance, and readability of Rust code. It was created in 2014 and named after the eponymous Microsoft Office feature. As of 2021, Clippy has more than 450 rules, which can be browsed online and filtered by category.

Versioning system

Following Rust 1.0, new features are developed in nightly versions which release on a daily basis. During each release cycle of six weeks, changes on nightly versions are released to beta, while changes from the previous beta version are released to a new stable version.

Every three years, a new "edition" is produced. Editions are released to provide an easy reference point for changes due to the frequent nature of Rust's train release schedule, and to provide a window to make limited breaking changes. Editions are largely compatible and migration to a new edition is trivialized with automated tooling.

IDE support

The most popular language server for Rust is rust-analyzer. The original language server, RLS was officially deprecated in favor of rust-analyzer in July 2022. These projects provide IDEs and text editors with more information about a Rust project, with basic features including autocompletion, and display of compilation errors while editing.

Performance

Rust aims "to be as efficient and portable as idiomatic C++, without sacrificing safety". Rust does not perform garbage collection, which allows it to be more efficient and performant than other memory-safe languages.

Rust provides two "modes": safe and unsafe. The safe mode is the "normal" one, in which most Rust is written. In unsafe mode, the developer is responsible for the correctness of the code, making it possible to create applications which require low-level features. It has been demonstrated empirically that unsafe Rust is not always more performant than safe Rust, and can even be slower in some cases.

Many of Rust's features are so-called zero-cost abstractions, meaning they are optimized away at compile time and incur no runtime penalty. Since Rust utilizes LLVM, any performance improvements in LLVM also carry over to Rust. Unlike C and C++, Rust allows re-organizing struct and enum element ordering. This can be done to reduce the size of structures in memory, for better memory alignment, and to improve cache access efficiency.

Adoption

See also: Category:Rust (programming language) software

According to the Stack Overflow Developer Survey in 2022, 9% of respondents have recently done extensive development in Rust. The survey has additionally named Rust the "most loved programming language" every year from 2016 to 2022 (inclusive), a ranking based on the number of current developers who express an interest in continuing to work in the same language. In 2022, Rust tied with Python for "most wanted technology" with 18% of developers not currently working in Rust expressing an interest in doing so.

Rust has been adopted for components at a number of major software companies, including Amazon, Discord, Dropbox, Facebook (Meta), Google (Alphabet), and Microsoft.

Web browsers and services

Early homepage of Mozilla's Servo browser engine

• Firefox has two projects written in Rust: the Servo parallel browser engine developed by Mozilla in collaboration with Samsung; and Quantum, which is composed of several sub-projects for improving Mozilla's Gecko browser engine.
• OpenDNS uses Rust in some of its internal projects.
• Deno, a secure runtime for JavaScript and TypeScript, is built with V8, Rust, and Tokio.
• Amazon Web Services has multiple projects written in Rust, including Firecracker, a virtualization solution, and Bottlerocket, a Linux distribution and containerization solution.
• Cloudflare's implementations of the QUIC protocol and firewall rules are written in Rust.
• Arti is a Rust implementation of Tor server in Rust by The Tor Project.

Operating systems

exa, a command-line alternative to ls, written in Rust

• Redox is a "full-blown Unix-like operating system" including a microkernel written in Rust.
• Theseus, an experimental operating system described as having "intralingual design": leveraging Rust's programming language mechanisms for implementing the OS.
• The Google Fuchsia capability-based operating system has components written in Rust, including a TCP/IP library.
• Stratis is a file system manager written in Rust for Fedora and RHEL.
• exa is a Unix/Linux command line alternative to ls written in Rust.
• Rust for Linux is a patch series started in 2021 for adding Rust support to the Linux kernel.

Other notable projects and platforms

Ruffle, a web emulator for Adobe Flash SWF files

• Discord uses Rust for portions of its backend, as well as client-side video encoding, to augment the core infrastructure written in Elixir.
• Microsoft Azure IoT Edge, a platform used to run Azure services and artificial intelligence on IoT devices, has components implemented in Rust.
• Polkadot is an open source blockchain platform and cryptocurrency written in Rust.
• Ruffle is an open-source SWF emulator written in Rust.
• TerminusDB, an open source graph database designed for collaboratively building and curating knowledge graphs, is written in Prolog and Rust.

Community

Some Rust users refer to themselves as Rustaceans (a pun on crustacean) and adopt an orange crab, Ferris, as their unofficial mascot.

Conferences

Rust's official website lists online forums, messaging platforms, and in-person meetups for the Rust community. Conferences dedicated to Rust development include:

• RustConf: an annual conference in Portland, Oregon. Held annually since 2016 (except in 2020 and 2021 because of the COVID-19 pandemic).
• Rust Belt Rust: a #rustlang conference in the Rust Belt
• RustFest: Europe's @rustlang conference
• RustCon Asia
• Rust LATAM
• Oxidize Global

Rust Foundation

Rust Foundation

Formation	February 8, 2021 (2021-02-08)
Founders	Amazon Web Services Google Huawei Microsoft Mozilla Foundation
Type	Nonprofit organization
Location	United States
Chairperson	Shane Miller
Executive Director	Rebecca Rumbul
Website	foundation.rust-lang.org

The Rust Foundation is a non-profit membership organization incorporated in United States, with the primary purposes of backing the technical project as a legal entity and helping to manage the trademark and infrastructure assets.

It was established on February 8, 2021, with five founding corporate members (Amazon Web Services, Huawei, Google, Microsoft, and Mozilla). The foundation's board is chaired by Shane Miller. Starting in late 2021, its Executive Director and CEO is Rebecca Rumbul. Prior to this, Ashley Williams was interim executive director.

Governance teams

The Rust project is composed of teams that are responsible for different subareas of the development. For example, the Core team is responsible for "Managing the overall direction of Rust, subteam leadership, and any cross-cutting issues," the Compiler team is responsible for "Developing and managing compiler internals and optimizations," and the Language team is responsible for "Designing and helping to implement new language features," according to the official website.

See also

• Comparison of programming languages
• History of programming languages
• List of programming languages
• List of programming languages by type

Further reading

• Klabnik, Steve; Nichols, Carol (2019-08-12). The Rust Programming Language (Covers Rust 2018). No Starch Press. ISBN 978-1-7185-0044-0. (online version)
• Blandy, Jim; Orendorff, Jason; Tindall, Leonora F. S. (2021-07-06). Programming Rust: Fast, Safe Systems Development. O'Reilly Media. ISBN 978-1-4920-5259-3.

External links

• Official website