IssueRaiser

Tracking issue for trait aliases

<!-- homu-ignore:start --> *[View all comments](https://triagebot.infra.rust-lang.org/gh-comments/rust-lang/rust/issues/41517)* <!-- homu-ignore:end --> This is a tracking issue for the feature *trait aliases* (originally specified in [RFC 1733](https://github.com/rust-lang/rfcs/pull/1733)). The feature gate for the issue is `#![feature(trait_alias)]`. > [!IMPORTANT] > The implementation of this feature is tracked separately in https://github.com/rust-lang/rust/issues/55628. ### 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 feature (MVP) - [x] #56485 — Bringing a trait alias into scope doesn't allow calling methods from its component traits (done in https://github.com/rust-lang/rust/pull/59166) - [x] #56488 — ICE with trait aliases and use items - [x] #57023 — Nightly Type Alias Compiler panic `unexpected definition: TraitAlias` - [x] #57059 — `INCOHERENT_AUTO_TRAIT_OBJECTS` future-compatibility warning (superseded by https://github.com/rust-lang/rust/pull/56481) - [ ] Document - [ ] Stabilize ### Unresolved questions - [ ] Should we really imply bounds on generic parameters other th

Posted by withoutboats on Apr 24, 2017, 10:45 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 trait aliases

withoutboatsApr 24, 2017, 10:45 PM

<!-- homu-ignore:start --> *[View all comments](https://triagebot.infra.rust-lang.org/gh-comments/rust-lang/rust/issues/41517)* <!-- homu-ignore:end --> This is a tracking issue for the feature *trait aliases* (originally specified in [RFC 1733](https://github.com/rust-lang/rfcs/pull/1733)). The feature gate for the issue is `#![feature(trait_alias)]`. > [!IMPORTANT] > The implementation of this feature is tracked separately in https://github.com/rust-lang/rust/issues/55628. ### 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 feature (MVP) - [x] #56485 — Bringing a trait alias into scope doesn't allow calling methods from its component traits (done in https://github.com/rust-lang/rust/pull/59166) - [x] #56488 — ICE with trait aliases and use items - [x] #57023 — Nightly Type Alias Compiler panic `unexpected definition: TraitAlias` - [x] #57059 — `INCOHERENT_AUTO_TRAIT_OBJECTS` future-compatibility warning (superseded by https://github.com/rust-lang/rust/pull/56481) - [ ] Document - [ ] Stabilize ### Unresolved questions - [ ] Should we really imply bounds on generic parameters other th

Comments (0)

No comments yet. Start the discussion.

Comment on this issue