IssueRaiser

Tracking issue for RFC 2515, "Permit impl Trait in type aliases"

This is a tracking issue for the RFC "Permit impl Trait in type aliases" (rust-lang/rfcs#2515) which is implemented under the following `#![feature(..)]` gates: - `type_alias_impl_trait` - `impl_trait_in_assoc_type`: https://github.com/rust-lang/rust/pull/110237 ### 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 - [x] Implement the RFC - [ ] Stabilize `-Znext-solver` https://github.com/rust-lang/rust/issues/107374 - [ ] Adjust documentation ([see instructions on rustc-guide][doc-guide]) - [ ] Stabilization PR ([see instructions on rustc-guide][stabilization-guide]) [stabilization-guide]: https://rust-lang.github.io/rustc-guide/stabilization_guide.html#stabilization-pr [doc-guide]: https://rust-lang.github.io/rustc-guide/stabilization_guide.html#documentation-prs ### Unresolved questions - [x] Exactly what should count as "defining uses" for opaque types? - [x] Should the set of "defining uses" for an opaque type in an impl be just items of the impl, or include nested items within the impl functions etc? ([see here for example](https://github.com/rust-lang/rust/pull/52650#discussion_r204893239)) - [

Posted by Centril on Jul 28, 2019, 6:12 AM

Tags

Related issues

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

github (Software)

Tracking issue for RFC 2515, "Permit impl Trait in type aliases"

CentrilJul 28, 2019, 6:12 AM

This is a tracking issue for the RFC "Permit impl Trait in type aliases" (rust-lang/rfcs#2515) which is implemented under the following `#![feature(..)]` gates: - `type_alias_impl_trait` - `impl_trait_in_assoc_type`: https://github.com/rust-lang/rust/pull/110237 ### 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 - [x] Implement the RFC - [ ] Stabilize `-Znext-solver` https://github.com/rust-lang/rust/issues/107374 - [ ] Adjust documentation ([see instructions on rustc-guide][doc-guide]) - [ ] Stabilization PR ([see instructions on rustc-guide][stabilization-guide]) [stabilization-guide]: https://rust-lang.github.io/rustc-guide/stabilization_guide.html#stabilization-pr [doc-guide]: https://rust-lang.github.io/rustc-guide/stabilization_guide.html#documentation-prs ### Unresolved questions - [x] Exactly what should count as "defining uses" for opaque types? - [x] Should the set of "defining uses" for an opaque type in an impl be just items of the impl, or include nested items within the impl functions etc? ([see here for example](https://github.com/rust-lang/rust/pull/52650#discussion_r204893239)) - [

Comments (0)

No comments yet. Start the discussion.

Comment on this issue