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

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

Tracking Issue for RFC 3762, "Make trait methods callable in const contexts" · Issue #143874 · rust-lang/rust · GitHub

This is a tracking issue for the RFC "3762" (rust-lang/rfcs#3762).
The feature gate for the issue is #![feature(const_trait_impl)].

Note

Questions about the usage of this feature should be directed to the t-compiler/project-const-traits Zulip channel. Use t-lang/effects and the RFC (until it gets accepted) to discuss the language feature and future extensions.

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.

• #[const_trait] attribute
• impl const Trait
• T: [const] Trait
• append_const_msg on rustc_on_unimplemented
• #[derive_const]
• trait Destruct

• Implement the RFC
• Add const trait Trait and migrate away from #[const_trait] parse const trait Trait #143879
• add a perf stress test for const trait impls and complex bounds that need solving
• Adjust documentation (see instructions on rustc-dev-guide)
• Style updates for any new syntax (nightly-style-procedure)
  • Style team decision on new formatting
  • Formatting for new syntax has been added to the Style Guide
  • (non-blocking) Formatting has been implemented in rustfmt
• Stabilization PR (see instructions on rustc-dev-guide)
  • Error against putting rustc_const_unstable attribute on const impls as they are now insta-stable.
  • Treat const trait default method bodies and const impl bodies as stable const fn bodies. We need to prevent accidentally stabilizing an implementation that uses unstable lang/lib const fn features.
  • Change Rustdoc to display [const] bounds or what syntax we decided it to be.

• #[derive_const] for custom derives (proc macros) Provide a way for derives to know if they were invoked with #[derive_const] #118304

• See Tracking issue for closed RFC 2632, impl const Trait for Ty and [const] (conditionally const) syntax (const_trait_impl) #67792 for previous tracking issue and its history
• Incomplete list of PRs implementing/refining the feature: https://github.com/rust-lang/rust/pulls?q=is%3Apr+label%3AF-const_trait_impl+is%3Aclosed+

rodrigocfd, nooriro, Filiprogrammer, KaranJain21, datawater and 3 morecarlocorradini, sukhmel, usbalbin, hanna-kruppe, connortsui20 and 25 morebjoernager

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