Rust Search
Find the best content on Rust, curated by the community; a
search engine for Rustaceans.
## Summary [summary]: #summary A new attribute can be placed on trait implementations: `#[do_not_recommend]`. This attribute will cause the compiler to never recommend this impl transitively as a way to implement another trait. For example,...
## Summary [summary]: #summary This RFC attempts to resolve some of the unresolved questions in [RFC 2045 (`target_feature`)]. In particular, it allows: * specifying `#[target_feature]` functions without making them `unsafe fn` * calling `#...
## Summary [summary]: #summary [RFC 243]: https://github.com/rust-lang/rfcs/blob/master/text/0243-trait-based-exception-handling.md#choice-of-keywords [RFC 243] left the choice of keyword for `catch { .. }` expressions unresolved. This RFC...
## Summary [summary]: #summary Stabilize the `#[used]` attribute which is used to force the compiler to keep static variables, even if not referenced by any other part of the program, in the output object file. ## Motivation [motivation]: #...
## Summary [summary]: #summary Rust has a number of code lints, both built into the compiler and provided through external tools, which provide guidelines for code style. The linter behavior can be customized by attaching attributes to regi...
## Summary [summary]: #summary Add async & await syntaxes to make it more ergonomic to write code manipulating futures. This has [a companion RFC](2592-futures.md) to add a small futures API to libstd and libcore. ## Motivation [motivation]...
## Summary [summary]: #summary This RFC introduces the `#[optimize]` attribute for controlling optimization level on a per-item basis. ## Motivation [motivation]: #motivation Currently, rustc has only a small number of optimization options...
## Summary [summary]: #summary Add a `dbg!($expr)` macro to the prelude (so that it doesn’t need to be imported) that prints its argument with some metadata (source code location and stringification) before returning it. This is a simpler a...
## Summary [summary]: #summary This RFC adds `core::hint::bench_black_box` (see [black box]), an identity function that hints the compiler to be maximally pessimistic in terms of the assumptions about what `bench_black_box` could do. [black...
## Summary [summary]: #summary This RFC gives users a way to control the discriminants of variants of all enumerations, not just the ones that are shaped like C-like enums (i.e. where all the variants have no fields). The change is minimal:...
## Summary [summary]: #summary Permit matching sub-slices and sub-arrays with the syntax `..`. Binding a variable to the expression matched by a subslice pattern can be done using syntax `<IDENT> @ ..` similar to the existing `<IDENT> @ <PA...
## Summary [summary]: #summary Add the methods `is_sorted`, `is_sorted_by` and `is_sorted_by_key` to `[T]`; add the methods `is_sorted` and `is_sorted_by` to `Iterator`. ## Motivation [motivation]: #motivation In quite a few situations, one...
## Summary [summary]: #summary Allow the use of `panic!`, `assert!` and `assert_eq!` within constants and report their evaluation as a compile-time error. ## Motivation [motivation]: #motivation It can often be desirable to terminate a cons...
## Summary [summary]: #summary Introduce new APIs to libcore / libstd to serve as safe abstractions for data which cannot be safely moved around. ## Motivation [motivation]: #motivation A longstanding problem for Rust has been dealing with...
## Summary [summary]: #summary Allow the use of `loop`, `while` and `while let` during constant evaluation. `for` loops are technically allowed, too, but can't be used in practice because each iteration calls `iterator.next()`, which is not...
## Summary [summary]: #summary This RFC proposes to allow access to enum variants through type aliases. This enables better abstraction/information hiding by encapsulating enums in aliases without having to create another enum type and requ...
## Summary [summary]: #summary Adds a *Prior art* section to the RFC template where RFC authors may discuss the experience of other programming languages and their communities with respect to what is being proposed. This section may also di...
## Summary [summary]: #summary The purpose of this RFC is to provide a framework for SIMD to be used on stable Rust. It proposes stabilizing x86-specific vendor intrinsics, but includes the scaffolding for other platforms as well as a futur...
## Summary [summary]: #summary This RFC allows safe implementations of `unsafe` trait methods. An `impl` may implement a trait with methods marked as `unsafe` without marking the methods in the `impl` as `unsafe`. This is referred to as *ov...
"Error types should be located near to their unit of fallibility."