IssueRaiser

Tracking issue for RFC 3519: `arbitrary_self_types`

<!-- homu-ignore:start --> *[View all comments](https://triagebot.infra.rust-lang.org/gh-comments/rust-lang/rust/issues/44874)* <!-- homu-ignore:end --> This is the tracking issue for RFC 3519: Arbitrary self types v2. The feature gate for this issue is `#![feature(arbitrary_self_types)]`. ### About tracking issues Tracking issues are used to record the overall progress of implementation. They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions. A tracking issue is however *not* meant for large scale discussion, questions, or bug reports about a feature. Instead, open a dedicated issue for the specific matter and add the relevant feature gate label. ### Steps [Current plan][] is: [Current plan]: https://github.com/rust-lang/rust/issues/44874#issuecomment-2122179688 * [x] **Fix the current lifetime elision bugs** * [x] **Search for potentially conflicting method candidates** * [x] **Block generic arbitrary self types**. * [x] **Introduce an `arbitrary_self_types_pointers` feature gate** * [x] **Rename the old `Receiver` trait** -- currently being run through crater * [x] **Land the new `Receiver` trait without it doing anything**. * [x] **Switch over the method resolution to use the `Receiver` trait, if the `arbitrary_self_types` feature is enabled**. The main event. * [ ] **Add [diagnostics](https://github.com/rust-lang/rust/issues/44874) for the `!Sized` case and the `NonNull` etc. cases.** * [ ] **Update the Rust ref

Posted by arielb1 on Sep 26, 2017, 8:52 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.4,500 issues0 comments

github (Sysadmin)

Tracking issue for RFC 3519: `arbitrary_self_types`

arielb1Sep 26, 2017, 8:52 PM

<!-- homu-ignore:start --> *[View all comments](https://triagebot.infra.rust-lang.org/gh-comments/rust-lang/rust/issues/44874)* <!-- homu-ignore:end --> This is the tracking issue for RFC 3519: Arbitrary self types v2. The feature gate for this issue is `#![feature(arbitrary_self_types)]`. ### About tracking issues Tracking issues are used to record the overall progress of implementation. They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions. A tracking issue is however *not* meant for large scale discussion, questions, or bug reports about a feature. Instead, open a dedicated issue for the specific matter and add the relevant feature gate label. ### Steps [Current plan][] is: [Current plan]: https://github.com/rust-lang/rust/issues/44874#issuecomment-2122179688 * [x] **Fix the current lifetime elision bugs** * [x] **Search for potentially conflicting method candidates** * [x] **Block generic arbitrary self types**. * [x] **Introduce an `arbitrary_self_types_pointers` feature gate** * [x] **Rename the old `Receiver` trait** -- currently being run through crater * [x] **Land the new `Receiver` trait without it doing anything**. * [x] **Switch over the method resolution to use the `Receiver` trait, if the `arbitrary_self_types` feature is enabled**. The main event. * [ ] **Add [diagnostics](https://github.com/rust-lang/rust/issues/44874) for the `!Sized` case and the `NonNull` etc. cases.** * [ ] **Update the Rust ref

Comments (0)

No comments yet. Start the discussion.

Comment on this issue