language design


Unsafe Code Guidelines A place to raise questions and discuss what kind of unsafe code should be legal.
Topic Replies Activity
About the language design category 2 March 25, 2019
Can we make a Rusty effect system? 9 January 25, 2020
Proposal about out-of-lifetime references 15 January 25, 2020
Annotations for zeroing the stack of "sensitive" functions which deal in transient secrets 29 January 23, 2020
[Pre-RFC] Zero-overhead exceptions 2 January 22, 2020
A #[repr] to allow an enum containing enums to use a single discriminant 12 January 22, 2020
Volatile and sensitive memory 90 January 22, 2020
Idea: A TupleJoin trait 5 January 19, 2020
Explicit negative impls to fix `Pin` soundness hole 21 January 18, 2020
The Pin unsoundness and `CoerceUnsized` 16 January 18, 2020
Idea: Naked Functions 2.0 28 January 16, 2020
Import system for the next language 13 January 15, 2020
Attribute macros on patterns 4 January 15, 2020
Operational semantics and high-level vs low-level 9 January 13, 2020
Closure: `value` moved, why `mut` needed? 19 October 21, 2019
[Pre-RFC] a `FnPointer` trait to permit writing more impls 6 January 10, 2020
Unsoundness in `Pin` 113 January 10, 2020
Pre-RFC: Runtime reflection 50 January 8, 2020
Cell, references, and struct layout 35 January 6, 2020
Pre-RFC: Supertrait item shadowing 16 January 6, 2020
Pre-RFC: Struct/union raw pointer field access 11 January 3, 2020
Idea: syntax sugar for else-less if blocks and Option<T> 7 January 2, 2020
Per-type static variables (take 2) 16 January 2, 2020
Should we add `Iterator::none`? 21 December 30, 2019
[Idea] allow unresolved symbols in statements of match arms that don't match (when matching on const) 6 December 30, 2019
[Pre-RFC] Add an `unmatched_variant` lint 12 December 22, 2019
[Idea] Immutable and exclusive reference 6 December 20, 2019
Destructing in const statement? 4 December 18, 2019
[Pre-RFC] named arguments 320 December 17, 2019
[Pre-RFC #2]: Inline assembly 161 December 16, 2019