Tracking Issue for RFC 2528: type-changing struct update syntax

[joshtriplett]

This is a tracking issue for RFC 2528 (rust-lang/rfcs#2528), type-changing struct update syntax.

The feature gate for the issue will be #![feature(type_changing_struct_update)].

There is a dedicated Zulip stream: #project-type-changing-struct-update

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

• Implementation: Implementation Issue for RFC 2528: type-changing struct update syntax #86555  #86618
• Inference failure with type_changing_struct_update #101970
• Adjust documentation (see instructions on rustc-dev-guide)
• Stabilization PR (see instructions on rustc-dev-guide)

Unresolved Questions

• Type inference: when implementing this, we need to confirm that it won't adversely affect type inference.

"Further generalization" in the RFC would be the subject of future RFCs, not something we need to track in this tracking issue.

Implementation history

• Feature gate: add feature flag for type_changing_struct_update #89730
• Implementation: implement rfc-2528 type_changing-struct-update #90035

[joshtriplett]

It looks like this has been implemented; are there any further known issues or blockers with it?

[Rua]

I'm eagerly awaiting stabilisation of this feature! Is there anything that still needs to be done?