<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Mar 31, 2020, at 12:48 PM, Simon Peyton Jones <<a href="mailto:simonpj@microsoft.com" class="">simonpj@microsoft.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0cm 0cm 0.0001pt 36pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">What features of the proposal document are actually a part of the proposal?<o:p class=""></o:p></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Well, all of it! </div></div></div></blockquote><div><br class=""></div><div>Good -- that's very clear, then. And it had been clear for some time (to me) -- it's just that I find it disagrees with the proposed text on the document, which reads:</div><div><br class=""></div><div>> The proposal is entirely about syntax; and specifically about</div>  introducing the form `r.x` for record field selection.  No changes<br class="">  to the type system, or any other aspect of the language, are<br class="">  proposed.  The original proposal was more elaborate, providing ways<br class="">  to update fields as well as set them, but was simplified to focus on<br class="">  the essentials.<div><br class=""></div><div>If we look at the proposal (<a href="https://github.com/shayne-fletcher-da/ghc-proposals/blob/record-dot-syntax/proposals/0000-record-dot-syntax.md#211-syntax" class="">https://github.com/shayne-fletcher-da/ghc-proposals/blob/record-dot-syntax/proposals/0000-record-dot-syntax.md#211-syntax</a>), we see a range of syntactic transformations. One of these repurposes record-update syntax, and assigns it new typing rules. To me, this changes the type system. Some of these rules propose new ways to update fields. (I see now you were thinking of the fact that syntax like `+=` has been abandoned. That's true, but I read the text above is referring to record-update.) So my reading of the rules leads to a different picture than the text above.</div><div><br class=""></div><div>But: if you agree (and it sounds like you do) that the proposal's text is definitive, I can update the text above to try to iron out these potential sources of confusion.</div><div><br class=""></div><div>Richard</div><div><br class=""></div><blockquote type="cite" class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">There are two pretty much orthogonal things going on<o:p class=""></o:p></div><ol start="1" type="1" style="margin-bottom: 0cm; margin-top: 0cm;" class=""><li class="MsoListParagraph" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">Syntax for record selection  r.x; this proposal<o:p class=""></o:p></li><li class="MsoListParagraph" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">Using overloading to resolve duplicate record labels, via getField/setField<o:p class=""></o:p></li></ol><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">It’s true (2) pretty much precludes selection/update for records with polymorphic fields (unless we have impredicativity, which I think we should ignore for now).  That has always been true.<o:p class=""></o:p></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">If you don’t want (2) then (1) is still useful.   Maybe the proposal should have different desugaring rules with and without OverloadedRecordFields.   That would be an additional box in the matrix, which I suppose we might want to fill in.<o:p class=""></o:p></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Including Shayne and Neil in this conversation.</div></div></blockquote><br class=""><blockquote type="cite" class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""></o:p></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Simon<o:p class=""></o:p></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class=""><o:p class=""> </o:p></span></div><div style="border-style: none none none solid; border-left-width: 1.5pt; border-left-color: blue; padding: 0cm 0cm 0cm 4pt;" class=""><div class=""><div style="border-style: solid none none; border-top-width: 1pt; border-top-color: rgb(225, 225, 225); padding: 3pt 0cm 0cm;" class=""><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><b class=""><span lang="EN-US" class="">From:</span></b><span lang="EN-US" class=""><span class="Apple-converted-space"> </span>Richard Eisenberg <<a href="mailto:rae@richarde.dev" class="">rae@richarde.dev</a>><span class="Apple-converted-space"> </span><br class=""><b class="">Sent:</b><span class="Apple-converted-space"> </span>31 March 2020 12:37<br class=""><b class="">To:</b><span class="Apple-converted-space"> </span>Simon Marlow <<a href="mailto:marlowsd@gmail.com" class="">marlowsd@gmail.com</a>><br class=""><b class="">Cc:</b><span class="Apple-converted-space"> </span>Simon Peyton Jones <<a href="mailto:simonpj@microsoft.com" class="">simonpj@microsoft.com</a>>; Neil Mitchell <<a href="mailto:ndmitchell@gmail.com" class="">ndmitchell@gmail.com</a>>; ghc-steering-committee <<a href="mailto:ghc-steering-committee@haskell.org" class="">ghc-steering-committee@haskell.org</a>>; Joachim Breitner <<a href="mailto:mail@joachim-breitner.de" class="">mail@joachim-breitner.de</a>>; Shayne Fletcher <<a href="mailto:shayne.fletcher@daml.com" class="">shayne.fletcher@daml.com</a>><br class=""><b class="">Subject:</b><span class="Apple-converted-space"> </span>Re: [ghc-steering-committee] Record dot syntax: vote results<o:p class=""></o:p></span></div></div></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div class=""><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Quoting from the document:<o:p class=""></o:p></div></div><div class=""><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">> The proposal is entirely about syntax; and specifically about<br class="">  introducing the form `r.x` for record field selection.  No changes<br class="">  to the type system, or any other aspect of the language, are<br class="">  proposed.  The original proposal was more elaborate, providing ways<br class="">  to update fields as well as set them, but was simplified to focus on<br class="">  the essentials.<o:p class=""></o:p></div><div class=""><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div></div><div class=""><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Is this fact enshrined in the proposal document? I view that as ground truth. And it describes, e.g., that (e { field = val }) now means (setField ...), which means that polymorphic record update is incompatible with -XRecordDotSyntax. What features of the proposal document are actually a part of the proposal?<o:p class=""></o:p></div></div><div class=""><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div></div><div class=""><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Otherwise, I am happy with the tone and content of the post.<o:p class=""></o:p></div></div><div class=""><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div></div><div class=""><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Thanks,<o:p class=""></o:p></div></div><div class=""><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Richard<o:p class=""></o:p></div></div><div class=""><div class=""><div class=""><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><br class=""><br class=""><o:p class=""></o:p></div><blockquote style="margin-top: 5pt; margin-bottom: 5pt;" class=""><div class=""><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">On Mar 31, 2020, at 11:40 AM, Simon Marlow <<a href="mailto:marlowsd@gmail.com" style="color: blue; text-decoration: underline;" class="">marlowsd@gmail.com</a>> wrote:<o:p class=""></o:p></div></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div class=""><div class=""><div class=""><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 9pt; font-family: Helvetica, sans-serif;" class="">On Tue, 31 Mar 2020 at 11:08, Simon Peyton Jones via ghc-steering-committee <<a href="mailto:ghc-steering-committee@haskell.org" style="color: blue; text-decoration: underline;" class="">ghc-steering-committee@haskell.org</a>> wrote:<o:p class=""></o:p></span></div></div><div class=""><blockquote style="border-style: none none none solid; border-left-width: 1pt; border-left-color: rgb(204, 204, 204); padding: 0cm 0cm 0cm 6pt; margin-left: 4.8pt; margin-right: 0cm;" class=""><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 9pt; font-family: Helvetica, sans-serif;" class="">Thanks Joachim.<span class="apple-converted-space"> </span><br class=""><br class="">Everyone: I have extended our choices document with a draft post to the Github thread.<br class=""><a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.google.com%2Fdocument%2Fd%2F1MgovHRUUNjbuM4nM8qEe308MfbAYRh2Q8PxFHl7iY74%2Fedit%3Fusp%3Dsharing&data=02%7C01%7Csimonpj%40microsoft.com%7Cd3178be33a584af741f808d7d567c97c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637212514046325345&sdata=LeXgcQuZXFbZ8qwKu%2FmvA0PYYMAv46JlTIuYHagDJcE%3D&reserved=0" target="_blank" style="color: blue; text-decoration: underline;" class="">https://docs.google.com/document/d/1MgovHRUUNjbuM4nM8qEe308MfbAYRh2Q8PxFHl7iY74/edit?usp=sharing</a><br class=""><br class="">Can you review it, for both tone and content?  You have edit permission, so by all means improve the wording.  Look for omissions.  I want to bring the discussion to a close, not re-ignite further debate, but be respectful of those who disagree.<o:p class=""></o:p></span></div></blockquote><div class=""><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 9pt; font-family: Helvetica, sans-serif;" class=""><o:p class=""> </o:p></span></div></div><div class=""><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 9pt; font-family: Helvetica, sans-serif;" class="">Before we accept the proposal I think we should have a precise description of the changes to the syntax. For example, we don't address the question of whether a field name can be an operator or not. We explicitly left these questions until later; wouldn't now be the right time to address them?<o:p class=""></o:p></span></div></div><div class=""><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 9pt; font-family: Helvetica, sans-serif;" class=""><o:p class=""> </o:p></span></div></div><div class=""><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 9pt; font-family: Helvetica, sans-serif;" class="">Also worth bringing up at this point, since we landed on C2a: Note 5 says<span class="apple-converted-space"> </span><o:p class=""></o:p></span></div></div><div class=""><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 9pt; font-family: Helvetica, sans-serif;" class=""><o:p class=""> </o:p></span></div></div><div style="margin-left: 30pt;" class=""><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="font-family: Arial, sans-serif;" class="">One mechanism for handling this is<span class="Apple-converted-space"> </span></span><span style="font-size: 9pt; font-family: Helvetica, sans-serif;" class=""><a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fshayne-fletcher-da%2Fghc-proposals%2Fblob%2Frecord-dot-syntax%2Fproposals%2F0000-record-dot-syntax.md%232322-parsing-of-field-selections&data=02%7C01%7Csimonpj%40microsoft.com%7Cd3178be33a584af741f808d7d567c97c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637212514046325345&sdata=Pcac6GXwXXCfPJt8u62ZTd1Vmq0hViqV2eRUPdYv358%3D&reserved=0" style="color: blue; text-decoration: underline;" class=""><span style="font-size: 11pt; font-family: Arial, sans-serif; color: rgb(17, 85, 204);" class="">given in the proposal</span></a></span><span style="font-family: Arial, sans-serif;" class="">.  It involves no changes to the lexer, but instead an adjacency test one production of the parser.</span><span style="font-size: 9pt; font-family: Helvetica, sans-serif;" class=""><o:p class=""></o:p></span></div></div><div class=""><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 9pt; font-family: Helvetica, sans-serif;" class=""><o:p class=""> </o:p></span></div></div><div class=""><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 9pt; font-family: Helvetica, sans-serif;" class="">I'm not sure about this as a language design. (1) it's an ad-hoc side-condition that can't be expressed in the lexical or context-free grammar (however there's precedent for this kind of thing in the form of the layout rule of course), and (2) it's quite a costly feature in terms of implementation effort to add to the language, because your AST needs complete and accurate source-span information. We can do it in GHC, and haskell-src-exts can do it nowadays, but earlier versions of haskell-src-exts before complete SrcSpanInfo was added wouldn't have been able to implement this rule. Arguably we're only accepting this as a GHC extension and not a Haskell extension in general, but as we know GHC is the testbed for future language extensions, so it's a good time to consider these issues.<o:p class=""></o:p></span></div></div><div class=""><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 9pt; font-family: Helvetica, sans-serif;" class=""><o:p class=""> </o:p></span></div></div><div class=""><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 9pt; font-family: Helvetica, sans-serif;" class="">The alternative of course is to go with some variant of<span class="apple-converted-space"> </span><o:p class=""></o:p></span></div></div><div class=""><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 9pt; font-family: Helvetica, sans-serif;" class=""><br class=""><br class=""><o:p class=""></o:p></span></div><div class=""><ol start="1" type="1" style="margin-bottom: 0cm;" class=""><ul type="circle" style="margin-bottom: 0cm;" class=""><li class="MsoNormal" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; vertical-align: baseline; font-variant-ligatures: normal; font-variant-caps: normal; font-variant-east-asian: normal; font-variant-position: normal;"><span style="font-family: Arial, sans-serif;" class="">Use the “tight infix” mechanism from<span class="Apple-converted-space"> </span><a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fghc-proposals%2Fghc-proposals%2Fpull%2F229&data=02%7C01%7Csimonpj%40microsoft.com%7Cd3178be33a584af741f808d7d567c97c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637212514046335298&sdata=r7FVNdNPqkn1N7N5NIViELWI%2F%2BjtdOjcArHCK%2BeP1oA%3D&reserved=0" style="color: blue; text-decoration: underline;" class=""><span style="color: rgb(17, 85, 204);" class="">this (accepted) GHC proposal</span></a><o:p class=""></o:p></span></li></ul></ol></div></div><div class=""><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 9pt; font-family: Helvetica, sans-serif;" class=""><o:p class=""> </o:p></span></div></div><div class=""><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 9pt; font-family: Helvetica, sans-serif;" class="">which is also an ad-hoc side-condition sadly, but could be implemented in the lexer.  Nevertheless, all this needs to be nailed down before the proposal can be accepted, IMO.<o:p class=""></o:p></span></div></div><div class=""><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 9pt; font-family: Helvetica, sans-serif;" class=""><o:p class=""> </o:p></span></div></div><div class=""><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 9pt; font-family: Helvetica, sans-serif;" class="">Cheers<o:p class=""></o:p></span></div></div><div class=""><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 9pt; font-family: Helvetica, sans-serif;" class="">Simon<o:p class=""></o:p></span></div></div><div class=""><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 9pt; font-family: Helvetica, sans-serif;" class=""><o:p class=""> </o:p></span></div></div><div class=""><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 9pt; font-family: Helvetica, sans-serif;" class=""> <o:p class=""></o:p></span></div></div><blockquote style="border-style: none none none solid; border-left-width: 1pt; border-left-color: rgb(204, 204, 204); padding: 0cm 0cm 0cm 6pt; margin-left: 4.8pt; margin-right: 0cm;" class=""><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 9pt; font-family: Helvetica, sans-serif;" class=""><br class="">Could you do so this week, by end Friday?   I propose to leave the votes recorded there, but when posting I'll move the post from the document (deleting it from there) to GitHub.<br class=""><br class="">I'm cc'ing Neil and Shayne, the authors.  Neil, Shayne: I think (and desperately hope!) you'll be content with this outcome.  Can you review my draft post too?<br class=""><br class="">Simon<br class=""><br class="">|  -----Original Message-----<br class="">|  From: ghc-steering-committee <<a href="mailto:ghc-steering-committee-bounces@haskell.org" target="_blank" style="color: blue; text-decoration: underline;" class="">ghc-steering-committee-bounces@haskell.org</a>><br class="">|  On Behalf Of Joachim Breitner<br class="">|  Sent: 30 March 2020 17:48<br class="">|  To: ghc-steering-committee <<a href="mailto:ghc-steering-committee@haskell.org" target="_blank" style="color: blue; text-decoration: underline;" class="">ghc-steering-committee@haskell.org</a>><br class="">|  Subject: Re: [ghc-steering-committee] Record dot syntax: vote results<br class="">| <span class="apple-converted-space"> </span><br class="">|  Dear Committe,<br class="">| <span class="apple-converted-space"> </span><br class="">|  thanks all for voting. The ranking of votes is now<br class="">| <span class="apple-converted-space"> </span><br class="">|        C2a > C2b > C4 > C1 > C7 > C6 > C3 > C5<br class="">| <span class="apple-converted-space"> </span><br class="">|  In particular C2a beats every other options by 7:4 or more, and is<br class="">|  therefore the result of this poll.<br class="">| <span class="apple-converted-space"> </span><br class="">|  You can see more statistics at<br class="">| <span class="apple-converted-space"> </span><a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.cond" target="_blank" style="color: blue; text-decoration: underline;" class="">https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.cond</a><br class="">| <span class="apple-converted-space"> </span><a href="https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Forcet.vote%2F&data=02%7C01%7Csimonpj%40microsoft.com%7Cd3178be33a584af741f808d7d567c97c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637212514046335298&sdata=rkSKjyK%2FJA8uBNPwPVr0%2Bv6aN8pzNwRVawnY6dsvnhw%3D&reserved=0" target="_blank" style="color: blue; text-decoration: underline;" class="">orcet.vote</a>%2FVote%2FAB23CE70AC%2F&amp;data=02%7C01%7Csimonpj%40microsoft.c<br class="">|  om%7Ce27e9c8f455b436e2bee08d7d4ca3538%7C72f988bf86f141af91ab2d7cd011db47%7<br class="">|  C1%7C0%7C637211837260982595&amp;sdata=LLWCxVjXxyLqcJUZ9iMgB%2B5QYGMuHFzJga<br class="">|  u9agTakiQ%3D&amp;reserved=0<br class="">| <span class="apple-converted-space"> </span><br class="">|  So, does this conclude this saga?<br class="">| <span class="apple-converted-space"> </span><br class="">|  Cheers,<br class="">|  Joachim<br class="">| <span class="apple-converted-space"> </span><br class="">|  --<br class="">|  Joachim Breitner<br class="">|   <span class="apple-converted-space"> </span><a href="mailto:mail@joachim-breitner.de" target="_blank" style="color: blue; text-decoration: underline;" class="">mail@joachim-breitner.de</a><br class="">| <span class="apple-converted-space"> </span><br class="">| <span class="apple-converted-space"> </span><a href="https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.joach" target="_blank" style="color: blue; text-decoration: underline;" class="">https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.joach</a><br class="">|  im-<br class="">| <span class="apple-converted-space"> </span><a href="https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fbreitner.de%2F&data=02%7C01%7Csimonpj%40microsoft.com%7Cd3178be33a584af741f808d7d567c97c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637212514046345257&sdata=O4msxBE2EnRV4wi3CIE7BuCTKnSLQc%2Fo8CUZhZ9TGMQ%3D&reserved=0" target="_blank" style="color: blue; text-decoration: underline;" class="">breitner.de</a>%2F&amp;data=02%7C01%7Csimonpj%<a href="https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2F40microsoft.com%2F&data=02%7C01%7Csimonpj%40microsoft.com%7Cd3178be33a584af741f808d7d567c97c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637212514046345257&sdata=c1iYCTMomIKk1T2lYXikl5lNyOYq%2F8YbpH6ZBtDAbX0%3D&reserved=0" target="_blank" style="color: blue; text-decoration: underline;" class="">40microsoft.com</a>%7Ce27e9c8f455b43<br class="">|  6e2bee08d7d4ca3538%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C6372118372<br class="">|  60982595&amp;sdata=GE%2BBYN7rA7zWgwuKlArv4PR%2Fm3IlmZ7PqWbGpgXUyms%3D&amp;<br class="">|  reserved=0<br class="">| <span class="apple-converted-space"> </span><br class="">| <span class="apple-converted-space"> </span><br class="">|  _______________________________________________<br class="">|  ghc-steering-committee mailing list<br class="">| <span class="apple-converted-space"> </span><a href="mailto:ghc-steering-committee@haskell.org" target="_blank" style="color: blue; text-decoration: underline;" class="">ghc-steering-committee@haskell.org</a><br class="">| <span class="apple-converted-space"> </span><a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail.has" target="_blank" style="color: blue; text-decoration: underline;" class="">https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail.has</a><br class="">| <span class="apple-converted-space"> </span><a href="https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fkell.org%2F&data=02%7C01%7Csimonpj%40microsoft.com%7Cd3178be33a584af741f808d7d567c97c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637212514046355208&sdata=%2B7s13qqQMwrJgTbslSo6ppv6ps8CF3VPOQ2U7HbXBMI%3D&reserved=0" target="_blank" style="color: blue; text-decoration: underline;" class="">kell.org</a>%2Fcgi-bin%2Fmailman%2Flistinfo%2Fghc-steering-<br class="">|  committee&amp;data=02%7C01%7Csimonpj%<a href="https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2F40microsoft.com%2F&data=02%7C01%7Csimonpj%40microsoft.com%7Cd3178be33a584af741f808d7d567c97c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637212514046355208&sdata=nHkhSCRoeCjBsRbmD96XnuzpwjFpW%2BHSXEeI7oDmAc8%3D&reserved=0" target="_blank" style="color: blue; text-decoration: underline;" class="">40microsoft.com</a>%7Ce27e9c8f455b436e2be<br class="">|  e08d7d4ca3538%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637211837260982<br class="">|  595&amp;sdata=nEx7qjYqnST1TA74HRkgK4O1zW3tvqpM4Dx4ECCig7I%3D&amp;reserved=<br class="">|  0<br class="">_______________________________________________<br class="">ghc-steering-committee mailing list<br class=""><a href="mailto:ghc-steering-committee@haskell.org" target="_blank" style="color: blue; text-decoration: underline;" class="">ghc-steering-committee@haskell.org</a><br class=""><a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail.haskell.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fghc-steering-committee&data=02%7C01%7Csimonpj%40microsoft.com%7Cd3178be33a584af741f808d7d567c97c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637212514046355208&sdata=a%2Btj9HkTV1ZQVM5Qfy%2FXTME01q824TGEpsjLFIhlOxE%3D&reserved=0" target="_blank" style="color: blue; text-decoration: underline;" class="">https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee</a><o:p class=""></o:p></span></div></blockquote></div></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 9pt; font-family: Helvetica, sans-serif;" class="">_______________________________________________<br class="">ghc-steering-committee mailing list<br class=""></span><a href="mailto:ghc-steering-committee@haskell.org" style="color: blue; text-decoration: underline;" class=""><span style="font-size: 9pt; font-family: Helvetica, sans-serif;" class="">ghc-steering-committee@haskell.org</span></a><span style="font-size: 9pt; font-family: Helvetica, sans-serif;" class=""><br class=""></span><a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail.haskell.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fghc-steering-committee&data=02%7C01%7Csimonpj%40microsoft.com%7Cd3178be33a584af741f808d7d567c97c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637212514046365166&sdata=5c1qnL0DD%2BPRpq0sLCfzersKVXGqTw9ENbk9JZODU8M%3D&reserved=0" style="color: blue; text-decoration: underline;" class=""><span style="font-size: 9pt; font-family: Helvetica, sans-serif;" class="">https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee</span></a></div></div></blockquote></div></div></div></div></div></blockquote></div><br class=""></body></html>