<div dir="ltr"><div dir="ltr"><div dir="ltr"><div>For what it's worth, I put this in my .zshrc</div><div><br></div><div>cleancore=(-ddump-simpl -dsuppress-coercions -dsuppress-var-kinds -dsuppress-idinfo -dsuppress-type-signatures -dsuppress-type-applications)<br></div><div><br></div><div>and then ghc $cleancore -c Foo.hs</div><div><br></div><div>but this is mainly for the use case of "I wonder if this thing is getting optimised the way I hope, let's have a look at the Core".</div><div><br></div><div>There's also this little tool which is aimed at the same kind of thing: <a href="https://github.com/shachaf/ghc-core">https://github.com/shachaf/ghc-core</a></div><div><br></div><div>So I'd say there's definitely a demand for something, but it's not entirely clear what the something is. Someone could make a proposal...<br></div></div></div></div><br><div class="gmail_quote"><div dir="ltr">On Sat, 6 Oct 2018 at 00:12, Simon Peyton Jones via ghc-devs <<a href="mailto:ghc-devs@haskell.org">ghc-devs@haskell.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Like Richard I use the uniques all the time.<br>
<br>
I'd prefer to leave it as-is, unless there is widespread support for a change<br>
<br>
S<br>
<br>
<br>
| -----Original Message-----<br>
| From: ghc-devs <<a href="mailto:ghc-devs-bounces@haskell.org" target="_blank">ghc-devs-bounces@haskell.org</a>> On Behalf Of Ömer Sinan<br>
| Agacan<br>
| Sent: 05 October 2018 20:02<br>
| To: <a href="mailto:rae@cs.brynmawr.edu" target="_blank">rae@cs.brynmawr.edu</a><br>
| Cc: ghc-devs <<a href="mailto:ghc-devs@haskell.org" target="_blank">ghc-devs@haskell.org</a>><br>
| Subject: Re: Shall we make -dsuppress-uniques default?<br>
| <br>
| > What do you say to GHC to get it to print the uniques that you don't<br>
| like?<br>
| <br>
| I usually use one of these: -ddump-simpl, -dverbose-core2core,<br>
| -ddump-simpl-iterations, -ddump-stg. All of these print variables with<br>
| unique<br>
| details and I literally never need those details. Rarely I use -ddump-cmm<br>
| too.<br>
| <br>
| Agreed that having different defaults in different dumps/traces might<br>
| work ..<br>
| <br>
| Ömer<br>
| <br>
| Richard Eisenberg <<a href="mailto:rae@cs.brynmawr.edu" target="_blank">rae@cs.brynmawr.edu</a>>, 5 Eki 2018 Cum, 21:54<br>
| tarihinde şunu yazdı:<br>
| ><br>
| > I'm in the opposite camp. More often than not, the biggest advantage of<br>
| dumps during GHC development is to see the uniques. Indeed, I often<br>
| ignore the actual names of variables and just work in my head with the<br>
| uniques.<br>
| ><br>
| > Perhaps the more complete answer is to fine-tune what settings cause<br>
| the uniques to be printed. -ddump-xx-trace should almost certainly.<br>
| Perhaps other modes needn't. What do you say to GHC to get it to print<br>
| the uniques that you don't like?<br>
| ><br>
| > Richard<br>
| ><br>
| > > On Oct 5, 2018, at 2:48 PM, Ömer Sinan Ağacan <<a href="mailto:omeragacan@gmail.com" target="_blank">omeragacan@gmail.com</a>><br>
| wrote:<br>
| > ><br>
| > > I asked this on IRC and didn't hear a lot of opposition, so as the<br>
| next step<br>
| > > I'd like to ask ghc-devs.<br>
| > ><br>
| > > I literally never need the details on uniques that we currently print<br>
| by<br>
| > > default. I either don't care about variables too much (when not<br>
| comparing the<br>
| > > output with some other output), or I need -dsuppress-uniques (when<br>
| comparing<br>
| > > outputs). The problem is I have to remember to add -dsuppress-uniques<br>
| if I'm<br>
| > > going to compare the outputs, and if I decide to compare outputs<br>
| after the fact<br>
| > > I need to re-generate them with -dsuppress-uniques. This takes time<br>
| and effort.<br>
| > ><br>
| > > If you're also of the same opinion I suggest making -dsuppress-<br>
| uniques default,<br>
| > > and providing a -dno-suppress-uniques (if it doesn't already exist).<br>
| > ><br>
| > > Ömer<br>
| > > _______________________________________________<br>
| > > ghc-devs mailing list<br>
| > > <a href="mailto:ghc-devs@haskell.org" target="_blank">ghc-devs@haskell.org</a><br>
| > ><br>
| <a href="https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmail.hask" rel="noreferrer" target="_blank">https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmail.hask</a><br>
| <a href="http://ell.org" rel="noreferrer" target="_blank">ell.org</a>%2Fcgi-bin%2Fmailman%2Flistinfo%2Fghc-<br>
| devs&data=02%7C01%7Csimonpj%<a href="http://40microsoft.com" rel="noreferrer" target="_blank">40microsoft.com</a>%7C07ec32bd26d149c457ab08d<br>
| 62af537c9%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636743630029759709<br>
| &sdata=4DVsRJ4Burv2%2BZGf38py%2FNRqM5j5%2FJAUkJPrUl7%2F%2Fm0%3D&r<br>
| eserved=0<br>
| ><br>
| _______________________________________________<br>
| ghc-devs mailing list<br>
| <a href="mailto:ghc-devs@haskell.org" target="_blank">ghc-devs@haskell.org</a><br>
| <a href="https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmail.hask" rel="noreferrer" target="_blank">https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmail.hask</a><br>
| <a href="http://ell.org" rel="noreferrer" target="_blank">ell.org</a>%2Fcgi-bin%2Fmailman%2Flistinfo%2Fghc-<br>
| devs&data=02%7C01%7Csimonpj%<a href="http://40microsoft.com" rel="noreferrer" target="_blank">40microsoft.com</a>%7C07ec32bd26d149c457ab08d<br>
| 62af537c9%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636743630029759709<br>
| &sdata=4DVsRJ4Burv2%2BZGf38py%2FNRqM5j5%2FJAUkJPrUl7%2F%2Fm0%3D&r<br>
| eserved=0<br>
_______________________________________________<br>
ghc-devs mailing list<br>
<a href="mailto:ghc-devs@haskell.org" target="_blank">ghc-devs@haskell.org</a><br>
<a href="http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs" rel="noreferrer" target="_blank">http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs</a><br>
</blockquote></div>