Re: record field names vs. -fwarn-unused-binds

On Tue, Nov 3, 2015 at 10:42 AM, Thomas Miedema wrote: > Through a patch by Oleg Grenrus (phadej), GHC 8 will have the following new > flags: > -fwarn-unused-top-binds > -fwarn-unused-local-binds > -fwarn-unused-pattern-binds > > So you'll be able to pick and choose. I suppose a record accesso

Re: [Haskell-cafe] record field names vs. -fwarn-unused-binds

On Tue, 3 Nov 2015, Evan Laforge wrote: I can work around by putting underscores on field names I haven't used yet, but it's a hassle to go edit them when I want to use them. I do it this way and I do not consider it a work-around. The underscore is just the shortest way to say that a record

Re: record field names vs. -fwarn-unused-binds

Through a patch by Oleg Grenrus (phadej), GHC 8 will have the following new flags: -fwarn-unused-top-binds -fwarn-unused-local-binds -fwarn-unused-pattern-binds So you'll be able to pick and choose. On Tue,

record field names vs. -fwarn-unused-binds

[ ccing haskell-cafe since while it's a ghc flag, I'll bet most compilers have an equivalent ] I really like -fwarn-unused-binds because it frequently finds bugs where I forgot to call something or use some value. If I put an export list on, it can find dead functions I forgot to delete. However,