-
-
Notifications
You must be signed in to change notification settings - Fork 14.8k
Support ConstArgKind::Paths for const struct/variant constructors #132985
Copy link
Copy link
Closed
Labels
C-enhancementCategory: An issue proposing an enhancement or a PR with one.Category: An issue proposing an enhancement or a PR with one.F-min_generic_const_args`#![feature(min_generic_const_args)]``#![feature(min_generic_const_args)]`T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.
Metadata
Metadata
Assignees
Labels
C-enhancementCategory: An issue proposing an enhancement or a PR with one.Category: An issue proposing an enhancement or a PR with one.F-min_generic_const_args`#![feature(min_generic_const_args)]``#![feature(min_generic_const_args)]`T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Requires encoding const ctors in MIR metadata (not currently done for some reason). May affect perf. cc #131081.
edit: BoxyUwU
We probably want to lower paths to const ctors directly to a
ConstKind::Valueto avoid needing to encode the MIR for const ctors. This is technically "lossy" lowering in some sense but it seems fine to me.