My favorites | Sign in
Project Home Wiki Issues Source
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 33: Auto-fix for Errors/Warnings
2 people starred this issue and may be notified of changes. Back to list
Status:  New
Owner:  nomin...@googlemail.com


Sign in to add a comment
 
Project Member Reported by nomin...@googlemail.com, Jun 24, 2009
Many warnings and errors issued by GHC can be fixed semi-automatically. 
For example:

 - An unused variable warning can be fixed by prefixing the variable with
an underscore.

 - Missing type signatures can be added automatically, but the user might
want to review the naming of type variables.

 - Errors that complain about a LANGUAGE pragma can be fixed, e.g.,
PatternGuards, TypeSynonymInstances, etc..  The suggested pragma might not
always be the best choice, though, e.g., ExistentialTypes vs.
Rank2Types/RankNTypes.

 - Some weird errors without helpful messages could be improved this way,
too.  E.g., adding the CPP pragma if the parser barfs on a #ifdef line.

GHC could be improved to use different types or constructors for different
error messages so error messages need not be matched with regexps.

Sign in to add a comment

Powered by Google Project Hosting