8f85b90ca6
As part of the "arbitrary self types v2" project, we are going to replace the current `Receiver` trait with a new mechanism based on a new, different `Receiver` trait. This PR renames the old trait to get it out the way. Naming is hard. Options considered included: * HardCodedReceiver (because it should only be used for things in the standard library, and hence is sort-of hard coded) * LegacyReceiver * TargetLessReceiver * OldReceiver These are all bad names, but fortunately this will be temporary. Assuming the new mechanism proceeds to stabilization as intended, the legacy trait will be removed altogether. Although we expect this trait to be used only in the standard library, we suspect it may be in use elsehwere, so we're landing this change separately to identify any surprising breakages. It's known that this trait is used within the Rust for Linux project; a patch is in progress to remove their dependency. This is a part of the arbitrary self types v2 project, https://github.com/rust-lang/rfcs/pull/3519 https://github.com/rust-lang/rust/issues/44874 r? @wesleywiser |
||
|---|---|---|
| .. | ||
| alloc_example.rs | ||
| alloc_system.rs | ||
| arbitrary_self_types_pointers_and_wrappers.rs | ||
| dst-field-align.rs | ||
| example.rs | ||
| mini_core_hello_world.rs | ||
| mini_core.rs | ||
| mod_bench.rs | ||
| std_example.rs | ||
| subslice-patterns-const-eval.rs | ||
| track-caller-attribute.rs | ||