internals
ideas (deprecated)
Semi-explicit coercion control with `~`
(10)
Pre-RFC: input! macro
(6)
A borrow operator
(16)
Optimized representations
(6)
[Pre-RFC] Allocators, take II
(11)
All of the things
(3)
Clone for closures
(2)
Recursively defining a type without using an Option
(3)
Was this idea for struct/enum unification considered?
(8)
[Pre-RFC] `fn` lifetimes
(9)
[Pre-RFC] Extend mutability control to control partial moves of objects
(4)
@ alias for self
(8)
[Pre-RFC] Function types
(2)
Inheritance structs
(6)
Self-referencing structs
(4)
[Pre-RFC] Filter out unit tests BEFORE compiling the crate for faster edit-compile-test loops
(4)
[Pre-RFC] Add a `Coerce` trait to get rid of the `.as_slice()` calls
(9)
A move semantics centric view of drops (Addressing problems of RFC PR 210, Take 3)
(2)
[Withdrawn] `~` as the early drop point marker? (Addressing problems of RFC PR 210, Take 2)
(8)
[Withdrawn] Introduce `ScopedLt` and `InferredLt` (A variant of RFC PR 210)
(2)
Auto-currying in Rust
(
2
)
(27)
`impl<T: Copy> Copy for &mut T`?
(4)
Syntax extension for static stack analysis
(8)
Rust's operator overloading doesn't scale
(6)
Runtime instance type disambiguation via TypeId?
(5)
A `range!´ macro
(19)
Custom extractors in Rust?
(2)
Making the type keyword more useful
(3)
Variadic Generics
(8)
Pass `&` references by value
(
2
)
(27)
← previous page
next page →
