<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"DejaVu Sans";
panose-1:2 11 6 3 3 8 4 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-ligatures:standardcontextual;
mso-fareast-language:EN-US;}
code
{mso-style-priority:99;
font-family:"Courier New";}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="en-NL" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Dear Amber Expert Group member,<br>
<br>
<o:p></o:p></p>
<p class="MsoNormal">I am a PhD candidate at Eindhoven University of Technology doing research into formally proving the correctness of automated restructurings of large legacy codebases.<br>
The features that have come with JDK21 have been very useful when it comes to quickly delivering robust code, especially JEP 440 and its sibling JEP 441.<br>
However, in JEP 440, it is noted that “<span lang="en-NL" style="font-size:10.0pt;font-family:"DejaVu Sans",sans-serif;color:black">the main change since the second preview is to remove support for record patterns appearing in the header of an enhanced </span><code><span lang="en-NL" style="font-size:10.0pt;color:black">for</span></code><span lang="en-NL" style="font-size:10.0pt;font-family:"DejaVu Sans",sans-serif;color:black"> statement.</span><span style="font-size:10.0pt;font-family:"DejaVu Sans",sans-serif;color:black">”.
</span><span style="font-size:10.0pt;color:black">I have tried my best to find the rationale behind this decision, but I can not find any comments on this on the internet, nor am I able to come up with a convincing argument, besides time/labor constraints,
myself.<br>
I certainly do not intend to start an argument on this decision, I am just hoping that perhaps one of the expert group members could give some explanation as to why it was decided to drop this feature.<br>
<br>
With kind regards,<br>
<br>
Flip van Spaendonck</span><o:p></o:p></p>
</div>
</body>
</html>