Tracking issue for specialization (RFC 1210)

<!-- homu-ignore:start --> *[View all comments](https://triagebot.infra.rust-lang.org/gh-comments/rust-lang/rust/issues/31844)* <!-- homu-ignore:end --> This is a tracking issue for specialization (rust-lang/rfcs#1210). Major implementation steps: - [x] Land https://github.com/rust-lang/rust/pull/30652 =) - [ ] Restrictions around lifetime dispatch (currently a **soundness hole**) - [ ] `default impl` (https://github.com/rust-lang/rust/issues/37653) - [ ] Integration with associated consts - [ ] Bounds not always properly enforced (https://github.com/rust-lang/rust/issues/33017) - [ ] Should we permit empty impls if parent has no `default` members? https://github.com/rust-lang/rust/issues/48444 - [ ] implement "always applicable" impls https://github.com/rust-lang/rust/issues/48538 - [ ] describe and test the precise cycle conditions around creating the specialization graph (see e.g. [this comment](https://github.com/rust-lang/rust/pull/70535#discussion_r401685535), which noted that we have some very careful logic here today) Unresolved questions from the RFC: - Should associated type be specializable at all? - When should projection reveal a `default type`? Never during typeck? Or when monomorphic? - Should default trait items be considered `default` (i.e. specializable)? - Should we have `default impl` (where all items are `default`) or `partial impl` (where `default` is opt-in); see https://github.com/rust-lang/rust/issues/37653#issuecomment-616116577 for some relevant

Posted by nikomatsakis on Feb 23, 2016, 5:35 PM

Tags

• github (Sysadmin)

Related issues

• Custom games stuck on "finding server" for all european servers
• Feature request: add ACP (Agent Client Protocol) stdio JSON-RPC mode
• Forza Horizon 6 (2483190)
• Turn off integrated browser for default
• Weekly updates are too frequent
• [BUG] Max 20x plan: 100% usage after 2 hours of light work (5 commits, no agents)