IssueRaiser

Tracking Issue for non-lifetime binders

This is a tracking issue for "non-lifetime binders" (https://github.com/rust-lang/types-team/issues/81). The feature gate for the issue is `#![feature(non_lifetime_binders)]`. ### 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 <!-- Include each step required to complete the feature. Typically this is a PR implementing a feature, followed by a PR that stabilises the feature. However for larger features an implementation could be broken up into multiple PRs. --> - [x] Initial implementation them - [ ] RFC needs to be written - [ ] Adjust documentation ([see instructions on rustc-dev-guide][doc-guide]) - [ ] Stabilization PR ([see instructions on rustc-dev-guide][stabilization-guide]) [stabilization-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#stabilization-pr [doc-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#documentation-prs ### Unresolved Questions - interaction with proposed fix for https://github.com/rust-lang/rust/issues/135011 None yet ### Implementation history * #107489

Posted by compiler-errors on Feb 17, 2023, 8:18 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.2,500 issues0 comments

reliability (Software)

Tracking Issue for non-lifetime binders

compiler-errorsFeb 17, 2023, 8:18 PM

This is a tracking issue for "non-lifetime binders" (https://github.com/rust-lang/types-team/issues/81). The feature gate for the issue is `#![feature(non_lifetime_binders)]`. ### 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 <!-- Include each step required to complete the feature. Typically this is a PR implementing a feature, followed by a PR that stabilises the feature. However for larger features an implementation could be broken up into multiple PRs. --> - [x] Initial implementation them - [ ] RFC needs to be written - [ ] Adjust documentation ([see instructions on rustc-dev-guide][doc-guide]) - [ ] Stabilization PR ([see instructions on rustc-dev-guide][stabilization-guide]) [stabilization-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#stabilization-pr [doc-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#documentation-prs ### Unresolved Questions - interaction with proposed fix for https://github.com/rust-lang/rust/issues/135011 None yet ### Implementation history * #107489

Comments (0)

No comments yet. Start the discussion.

Comment on this issue