<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Yes, I agree that we need functions in both directions. I support this proposal.<div class=""><br class=""></div><div class="">Richard<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Mar 8, 2019, at 12:03 PM, Iavor Diatchki <<a href="mailto:iavor.diatchki@gmail.com" class="">iavor.diatchki@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">I agree that we should probably accept this.<div class=""><br class=""></div><div class="">I wonder if there are cases where one might one to go in the other direction, i.e., do we also need a function: `Code a -> Q (TExp a)`?</div><div class=""><br class=""></div><div class="">-Iavor</div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Mar 8, 2019 at 12:51 AM Simon Peyton Jones via ghc-steering-committee <<a href="mailto:ghc-steering-committee@haskell.org" class="">ghc-steering-committee@haskell.org</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div lang="EN-GB" class="">
<div class="gmail-m_-6279921378493960975WordSection1"><p class="MsoNormal"><span class="">Yes, I agree.<u class=""></u><u class=""></u></span></p><p class="MsoNormal"><span class=""><u class=""></u> <u class=""></u></span></p><p class="MsoNormal"><span class="">Simon<u class=""></u><u class=""></u></span></p><p class="MsoNormal"><span class=""><u class=""></u> <u class=""></u></span></p>
<div style="border-top:none;border-right:none;border-bottom:none;border-left:1.5pt solid blue;padding:0cm 0cm 0cm 4pt" class="">
<div class="">
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(225,225,225);padding:3pt 0cm 0cm" class=""><p class="MsoNormal"><b class=""><span lang="EN-US" class="">From:</span></b><span lang="EN-US" class=""> ghc-steering-committee <<a href="mailto:ghc-steering-committee-bounces@haskell.org" target="_blank" class="">ghc-steering-committee-bounces@haskell.org</a>>
<b class="">On Behalf Of </b>Vitaly Bragilevsky<br class="">
<b class="">Sent:</b> 08 March 2019 06:41<br class="">
<b class="">To:</b> ghc-steering-committee <<a href="mailto:ghc-steering-committee@haskell.org" target="_blank" class="">ghc-steering-committee@haskell.org</a>><br class="">
<b class="">Subject:</b> [ghc-steering-committee] #195: Make Q (TExp a) into a newtype, rec: accept<u class=""></u><u class=""></u></span></p>
</div>
</div><p class="MsoNormal"><u class=""></u> <u class=""></u></p>
<div class=""><p class="MsoNormal">Hi everyone, <u class=""></u><u class=""></u></p>
<div class=""><p class="MsoNormal"><u class=""></u> <u class=""></u></p>
</div>
<div class=""><p class="MsoNormal">Matthew Pickering proposed to make Q (TExp a) into a newtype called Code. <u class=""></u><u class=""></u></p>
</div>
<div class=""><p class="MsoNormal">Proposal #195: <a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fghc-proposals%2Fghc-proposals%2Fblob%2F22e97d7693edb0b3676c948a123e57ea93c462e3%2Fproposals%2F0000-code-texp.rst&data=02%7C01%7Csimonpj%40microsoft.com%7C283dee8b70474ae9761308d6a3910fb5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636876240764020521&sdata=Cq32fdykV9oonakOOFbAnV7LulmupHXHq0p2c9raKFs%3D&reserved=0" target="_blank" class="">https://github.com/ghc-proposals/ghc-proposals/blob/22e97d7693edb0b3676c948a123e57ea93c462e3/proposals/0000-code-texp.rst</a><u class=""></u><u class=""></u></p>
</div>
<div class=""><p class="MsoNormal">Pull request discussion: <a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fghc-proposals%2Fghc-proposals%2Fpull%2F195&data=02%7C01%7Csimonpj%40microsoft.com%7C283dee8b70474ae9761308d6a3910fb5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636876240764030529&sdata=6CqagCiMbgVgSgmWeLTcDbauGsB111fn7DOyuMiXemI%3D&reserved=0" target="_blank" class="">https://github.com/ghc-proposals/ghc-proposals/pull/195</a><u class=""></u><u class=""></u></p>
</div>
<div class=""><p class="MsoNormal"><u class=""></u> <u class=""></u></p>
</div>
<div class=""><p class="MsoNormal">It looks like the motivation behind this proposal boils down to the convenience of writing instances which seems a good thing. The minor problem I see is the proposed name "Code" as it looks a little bit too abstract for Typed Template
Haskell expressions. Nevertheless, I recommend to accept the proposal as it is. Silence is understood as agreement.<u class=""></u><u class=""></u></p>
</div>
<div class=""><p class="MsoNormal"><u class=""></u> <u class=""></u></p>
</div>
<div class=""><p class="MsoNormal">Regards, <u class=""></u><u class=""></u></p>
</div>
<div class=""><p class="MsoNormal">Vitaly<u class=""></u><u class=""></u></p>
</div>
</div>
</div>
</div>
</div>
_______________________________________________<br class="">
ghc-steering-committee mailing list<br class="">
<a href="mailto:ghc-steering-committee@haskell.org" target="_blank" class="">ghc-steering-committee@haskell.org</a><br class="">
<a href="https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee" rel="noreferrer" target="_blank" class="">https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee</a><br class="">
</blockquote></div>
_______________________________________________<br class="">ghc-steering-committee mailing list<br class=""><a href="mailto:ghc-steering-committee@haskell.org" class="">ghc-steering-committee@haskell.org</a><br class="">https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee<br class=""></div></blockquote></div><br class=""></div></body></html>