This is a tracking issue for the feature return type notation specified in rust-lang/rfcs#3654.
The feature gate for the issue is #![feature(return_type_notation)].

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

• Implement the feature
  • Support RTN in associated type bounds (Initial support for return type notation (RTN) #109010)
  • Support RTN with (un-)qualified path syntax (e.g. where T::method(): Send) Implement Return Type Notation (RTN)'s path form in where clauses #129629
• Author RFC: RFC: Return Type Notation rfcs#3654
• Adjust documentation (see instructions on rustc-dev-guide)
• Stabilization PR (see instructions on rustc-dev-guide)

Unresolved questions

• Does stabilizing T::foo(..) notation as a standalone type create a confusing inconsistency with -> () shorthand?

Experimental results

Part of the goal of the experimental process is to identify benefits but also concerns that need to be addressed in the RFC.

• Alternative: typeof syntax.
• Concerns raised by lcnr

Implementation history

• Initial support for return type notation (RTN) #109010