SE-0544: Mutation and consumption in non-Copyable type deinits

Hello, Swift community.

The review of SE-0544: Mutation and consumption in non-Copyable type deinits begins now and runs through August 24th, 2026.

Reviews are an important part of the Swift evolution process. All review feedback should be either on this forum thread or, if you would like to keep your feedback private, directly to me as the review manager by email or forums DM. When contacting me as the review manager directly, please put "[SE-0544]" at the start of the subject.

What goes into a review?

The goal of the review process is to improve the proposal under review through constructive criticism and, eventually, determine the direction of Swift. When writing your review, here are some questions you might want to answer in your review:

  • What is your evaluation of the proposal?
  • Is the problem being addressed significant enough to warrant a change to Swift?
  • Does this proposal fit well with the feel and direction of Swift?
  • If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?
  • How much effort did you put into your review? A glance, a quick reading, or an in-depth study?

More information about the Swift evolution process is available in the evolution repository.

Thanks in advance for your review!

John McCall
Review Manager

9 Likes

This looks good to me. The restriction to only mutating parts of self seems like a reasonable way to avoid accidental resurrection.

+1 makes sense to me