Warnings for unitialized fields

[nobody]

Would it be possible to add flag to disable warnings for unitialized fields just when using constructor with zero fields? I mean, if I use

  Foo {}

to construct empty record, it is a bit unpleasant that I get flooded by dozens of useless warnings; but I don't want to disable them -- they are useful when I forget to initialize some field(s).

Zdenek Dvorak

[simonmar]

Not clear if this is a good idea, but we'll leave it here anyway.

[ste]

A proposition for this feature request

[ste]

To get started with ghc hacking I created this patch. If this patch (or something similar) should be added to ghc, just tell me and I will add the necessary documentation and test cases. (This patch breaks test case ds041.hs due to a changed warning text.)

[simonpj]

Thanks for contriubting a patch.

However, I'm not clear of the original intent here. Consider

data T = T { x,y::Int }
f = T { x = 3 }
g = T {}

It would be very odd to get a warning from f but not from g. I'm not sure this is what the original requester was asking. I thought he didn't want a warning when T had zero fields -- and indeed you don't get a warning then.

Puzzled.

Simon

[igloo]

There doesn't seem to be a consensus that anything should be done, so I'm closing this ticket.