Rust Search

Find the best content on Rust, curated by the community; a search engine for Rustaceans.
#3668
Feature Name: async_closure1 2 Start Date: 2024-06-25 RFC PR: rust-lang/rfcs#3668 Tracking Issue: rust-lang/rust#62290 Summary This RFC adds an async bound modifier to the Fn family of trait bounds. The combination currently desugars to a s...
rust-lang.github.io Updates from the Rust Project 2024-12-18 ~26 min read
#3593
Feature Name: unprefixed_guarded_strings Start Date: 2024-03-24 RFC PR: rust-lang/rfcs#3593 Tracking Issue: rust-lang/rust#123735 Summary Beginning with the 2024 edition, reserve the syntax #"foo"#, as a way of future-proofing against futur...
rust-lang.github.io Updates from the Rust Project 2024-10-16 ~3 min read
#3695
Feature Name: cfg_boolean_literals Start Date: 2024-09-16 RFC PR: rust-lang/rfcs#3695 Tracking Issue: rust-lang/rust#131204 Summary Allow true and false boolean literals as cfg predicates, i.e. cfg(true)/cfg(false). Motivation Often, we may...
rust-lang.github.io Updates from the Rust Project 2024-10-09 ~2 min read
#3550
Feature Name: new_range Start Date: 2023-12-18 RFC PR: rust-lang/rfcs#3550 Tracking Issue: rust-lang/rust#123741 Summary Change the range operators a..b, a.., and a..=b to resolve to new types std::range::Range, std::range::RangeFrom, and s...
rust-lang.github.io Updates from the Rust Project 2024-07-10 ~16 min read
#2289
Feature Name: associated_type_bounds Start Date: 2018-01-13 RFC PR: rust-lang/rfcs#2289 Rust Issue: rust-lang/rust#52662 Summary Introduce the bound form MyTrait<AssociatedType: Bounds>, permitted anywhere a bound of the form MyTrait<Associ...
rust-lang.github.io Updates from the Rust Project 2024-03-20 ~4 min read
#3373
Feature Name: N/A Start Date: 2022-01-19 RFC PR: rust-lang/rfcs#3373 Tracking Issue: rust-lang/rust#120363 Summary Add a warn-by-default lint for items inside functions or expressions that implement methods or traits that are visible outsid...
rust-lang.github.io Updates from the Rust Project 2024-02-28 ~2 min read
Rust API Guidelines
Rust API Guidelines This is a set of recommendations on how to design and present APIs for the Rust programming language. They are authored largely by the Rust library team, based on experiences building the Rust standard library and other...
rust-lang.github.io Rust API Guidelines Book 2024-01-01 ~1 min read
Rust API Guidelines Checklist
Rust API Guidelines Checklist • Naming (crate aligns with Rust naming conventions) • [ ] Casing conforms to RFC 430 (C-CASE) • [ ] Ad-hoc conversions follow as_, to_, into_ conventions (C-CONV) • [ ] Getter names follow Rust convention (C-G...
rust-lang.github.io Rust API Guidelines Book 2024-01-01 ~3 min read
Naming
Naming Casing conforms to RFC 430 (C-CASE) Basic Rust naming conventions are described in RFC 430. In general, Rust tends to use UpperCamelCase for "type-level" constructs (types and traits) and snake_case for "value-level" constructs. More...
rust-lang.github.io Rust API Guidelines Book 2024-01-01 ~7 min read
Interoperability
Interoperability Types eagerly implement common traits (C-COMMON-TRAITS) Rust's trait system does not allow orphans: roughly, every impl must live either in the crate that defines the trait or the implementing type. Consequently, crates tha...
rust-lang.github.io Rust API Guidelines Book 2024-01-01 ~7 min read
Macros
Macros Input syntax is evocative of the output (C-EVOCATIVE) Rust macros let you dream up practically whatever input syntax you want. Aim to keep input syntax familiar and cohesive with the rest of your users' code by mirroring existing Rus...
rust-lang.github.io Rust API Guidelines Book 2024-01-01 ~3 min read
Documentation
Documentation Crate level docs are thorough and include examples (C-CRATE-DOC) See RFC 1687. All items have a rustdoc example (C-EXAMPLE) Every public module, trait, struct, enum, function, method, macro, and type definition should have an...
rust-lang.github.io Rust API Guidelines Book 2024-01-01 ~6 min read
Predictability
Predictability Smart pointers do not add inherent methods (C-SMART-PTR) For example, this is why the Box::into_raw function is defined the way it is. impl<T> Box<T> where T: ?Sized { fn into_raw(b: Box<T>) -> *mut T { /* ... */ } } let boxe...
rust-lang.github.io Rust API Guidelines Book 2024-01-01 ~5 min read
Flexibility
Flexibility Functions expose intermediate results to avoid duplicate work (C-INTERMEDIATE) Many functions that answer a question also compute interesting related data. If this data is potentially of interest to the client, consider exposing...
rust-lang.github.io Rust API Guidelines Book 2024-01-01 ~5 min read
Type safety
Type safety Newtypes provide static distinctions (C-NEWTYPE) Newtypes can statically distinguish between different interpretations of an underlying type. For example, a f64 value might be used to represent a quantity in miles or in kilomete...
rust-lang.github.io Rust API Guidelines Book 2024-01-01 ~5 min read
Dependability
Dependability Functions validate their arguments (C-VALIDATE) Rust APIs do not generally follow the robustness principle: "be conservative in what you send; be liberal in what you accept". Instead, Rust code should enforce the validity of i...
rust-lang.github.io Rust API Guidelines Book 2024-01-01 ~2 min read
Debuggability
Debuggability All public types implement Debug (C-DEBUG) If there are exceptions, they are rare. Debug representation is never empty (C-DEBUG-NONEMPTY) Even for conceptually empty values, the Debug representation should never be empty. let...
rust-lang.github.io Rust API Guidelines Book 2024-01-01 ~1 min read
Future proofing
Future proofing Sealed traits protect against downstream implementations (C-SEALED) Some traits are only meant to be implemented within the crate that defines them. In such cases, we can retain the ability to make changes to the trait in a...
rust-lang.github.io Rust API Guidelines Book 2024-01-01 ~4 min read
Necessities
Necessities Public dependencies of a stable crate are stable (C-STABLE) A crate cannot be stable (>=1.0.0) without all of its public dependencies being stable. Public dependencies are crates from which types are used in the public API of th...
rust-lang.github.io Rust API Guidelines Book 2024-01-01 ~2 min read
External links
External links • RFC 199 - Ownership naming conventions • RFC 344 - Naming conventions • RFC 430 - Naming conventions • RFC 505 - Doc conventions • RFC 1574 - Doc conventions • RFC 1687 - Crate-level documentation • Elegant Library APIs in...
rust-lang.github.io Rust API Guidelines Book 2024-01-01 ~1 min read
"In many cases, it is possible to completely rearchitect the underlying code while leaving the public API as-is, and without introducing new bugs. I've..."
— Jay Oster on rust-users

Search tips

Type anything to search across articles, videos (including conference talks), podcasts, and research. These operators give you finer control — click an example to try it.

Find pages containing all your words. Pages where the words appear together rank higher.
Quote part of your query to keep those words together as an exact phrase within a larger search.
Wrap the whole query in quotes for a verbatim search that matches text exactly, punctuation and all — perfect for Rust syntax. Needs at least 3 characters.
Limit results to a single site. Works on its own () too. One site: per search.

Use the tabs and filters above the results to narrow by content type, publication year, and sort order.