Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/rust-lang/rust/issues/63066 below:

Meta tracking issue for `impl Trait` · Issue #63066 · rust-lang/rust · GitHub

This issue tracks the progress of impl Trait in general.

This issue is not for discussion about specific extensions to impl Trait and only exists to provide links to other places that track the progress of specific issues. If you wish to discuss some subject related to impl Trait, please find an existing appropriate issue below or create an new issue and comment here with a link to the newly created issue.

The impl Trait related issues currently on deck are as follows:

• Label A-impl-trait
• Permit type Foo = impl Bar;. Tracking issue for RFC 2515, "Permit impl Trait in type aliases" #63063
  • Permit type Foo = impl Bar; in trait definitions. Tracking issue for RFC 2532, "Associated type defaults" #29661
• In const and static items and let bindings. Tracking issue for impl Trait in const and static items and let bindings #63065
• Member constraints in region inference: Tracking issue for member constraints in region inference #61997
• Existential lifetimes. Tracking issue for existential lifetimes #60670
• Support lifetime elision in argument position. Argument-position impl Trait requires a named lifetime #49287
• Should we allow impl Trait after -> in fn types or parentheses sugar? [impl Trait] Should we allow impl Trait after -> in fn types or parentheses sugar? #45994
• Do we have to impose a DAG across all functions to allow for auto-safe leakage, or can we use some kind of deferral.
  • Discussion: Implement impl Trait in return type position by anonymization. #35091 (comment)
  • Present semantics: DAG.
• Should we permit specifying types if some parameters are implicit and some are explicit? e.g., fn foo<T>(x: impl Iterator<Item = T>>)?
  • Current behavior: An error to specify types
  • Other alternatives: [treat impl Trait as arguments in the list, permitting migration]
• Some concerns about nested impl Trait usage

Open RFCs:

None.

Avi-D-coder, crlf0710, dnrusakov, sachaarbonel, andysalerno and 66 moreschneiderfelipe and ManuelSopenaBallesterosrubik, NeoLegends, hectorj, jgarvin, ahlinc and 5 moreschneiderfelipe, I0x4dI and ManuelSopenaBallesterosschneiderfelipe and ManuelSopenaBallesteros

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4