rust-lang / rust-lang/rust

Tracking Issue for RFC 3591: `use`ing associated items from traits

Open
#134,691 11 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

B-RFC-approved B-RFC-implemented C-tracking-issue F-import_trait_associated_functions S-tracking-needs-to-bake T-lang
Dominant language
Rust
Stars
119k
Forks
16.1k
PR merge metrics
PR metrics pending

Description

This is a tracking issue for the RFC "Add support for use Trait::func" (rust-lang/rfcs#3591).
The feature gate for the issue is #![feature(import_trait_associated_functions)].

[!IMPORTANT]
Differences from RFC: You are allowed to glob-import associated items (::*) and you're allowed to import associated types (however, referencing the import will always lead to an ambiguity since the self type & trait can't be deduced from context (and likely never will, at least not until <_>::AssocTy works, cc https://github.com/rust-lang/rust/issues/22519)). Context / rationale: rust-lang/rust#3591.

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.
Discussion comments will get marked as off-topic or deleted.
Repeated discussions on the tracking issue may lead to the tracking issue getting locked.

Steps
Unresolved Questions
Implementation history

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked rustc-dev-guide documentation and stabilization-guide instructions, then review src/doc/style-guide and the nightly-style-procedure for the remaining documentation and formatting work. Done means the documentation is adjusted, new syntax has Style Guide formatting, and a stabilization PR is prepared.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
compilers, documentation
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.