>
> S
>
>
> | -Original Message-
> | From: ghc-devs On Behalf Of Ömer Sinan
> | Agacan
> | Sent: 05 October 2018 20:02
> | To: r...@cs.brynmawr.edu
> | Cc: ghc-devs
> | Subject: Re: Shall we make -dsuppress-uniques default?
> |
> | > What do you say
t: Re: Shall we make -dsuppress-uniques default?
|
| > What do you say to GHC to get it to print the uniques that you don't
| like?
|
| I usually use one of these: -ddump-simpl, -dverbose-core2core,
| -ddump-simpl-iterations, -ddump-stg. All of these print variables with
| unique
| details an
> What do you say to GHC to get it to print the uniques that you don't like?
I usually use one of these: -ddump-simpl, -dverbose-core2core,
-ddump-simpl-iterations, -ddump-stg. All of these print variables with unique
details and I literally never need those details. Rarely I use -ddump-cmm too.
I'm in the opposite camp. More often than not, the biggest advantage of dumps
during GHC development is to see the uniques. Indeed, I often ignore the actual
names of variables and just work in my head with the uniques.
Perhaps the more complete answer is to fine-tune what settings cause the
un
I asked this on IRC and didn't hear a lot of opposition, so as the next step
I'd like to ask ghc-devs.
I literally never need the details on uniques that we currently print by
default. I either don't care about variables too much (when not comparing the
output with some other output), or I need -d
