Separate warnings for unused local and top-level bindings

I'd like separate warnings for local and top-level
unused binds.  I often have "unused" top-level
functions which I use from ghci.  I'd like to avoid
warnings for
these while retaining the warnings for unused local
bindings (which can always be eliminated by prefix the
name with an underscore.)

changed weight to 0

added Tfeature request Trac import labels

changed title from RFE:Separate unused-binds local/top-levl to RFE:Separate unused-binds local/top-level

Logged In: YES 
user_id=48280

Moved to feature requests

mentioned in commit 334ce30e

changed the description

Trac metadata

Trac field	Value
Operating system	- → Unknown
Architecture	- → Unknown

Trac metadata

Trac field	Value
Architecture	Unknown → Unknown/Multiple

Trac metadata

Trac field	Value
Operating system	Unknown → Unknown/Multiple

mentioned in issue #3283

assigned to @trac-igloo and unassigned @trac-nobody

unassigned @trac-igloo

Trac metadata

Trac field	Value
Component	None → Compiler

changed title from RFE:Separate unused-binds local/top-level to Separate warnings for unused local and top-level bindings

Would any developers care to guess at the difficulty of this feature? Could this make a good project for someone just starting to get their feet wet hacking on ghc?

Trac metadata

Trac field	Value
TypeOfFailure	- → OtherFailure

I doubt the usefulness of this feature since any top-level function that is mentioned in the export list of the module won't trigger a warning. It is confusing to see dead code in a module and so top-level functions that aren't used should probably just be commented out.

However, this feature does come handy when using records: it often happens that a field name isn't used in a module, hence triggering a warning.

Replying to [ticket:17#comment:37403 byorgey]:

Would any developers care to guess at the difficulty of this feature? Could this make a good project for someone just starting to get their feet wet hacking on ghc?

I'd say so. It would probably be worth discussing the design on the cvs-ghc list first, though.

Note that you can simply prefix those "used from GHCi only top-level bindings" with an underscore as a workaround until this gets implemented.

Trac metadata

Trac field	Value
Related	→ #3283

added newcomer label

Trac metadata

Trac field	Value
Differential revisions	→ D591

mentioned in commit aead0190

closed

Merged, thanks!

Trac metadata

Trac field	Value
Resolution	ResolvedNoReason → ResolvedFixed

changed milestone to %8.0.1

Milestone renamed

mentioned in commit 3783b0d0

mentioned in commit c6fbac6a

added Plow label

mentioned in issue #19792 (closed)

mentioned in issue #19829 (closed)