#7162: RULES that never fire (automatically)
---------------------------------+------------------------------------------
Reporter: andygill | Owner:
Type: feature request | Status: patch
Priority: normal | Milestone:
Component: Compiler | Version: 7.4.2
Keywords: | Os: Unknown/Multiple
Architecture: Unknown/Multiple | Failure: None/Unknown
Difficulty: Unknown | Testcase:
Blockedby: | Blocking:
Related: |
---------------------------------+------------------------------------------
Changes (by afarmer):
* status: new => patch
Comment:
Here is a patch that implements this functionality (with [~] meaning never
automatically fire), as well as a patch to the testsuite to verify the
parser works.
I've built HERMIT against head (with this patch applied) and verified that
we can still use RULES that are marked to never fire (at both ends of the
optimization pipeline). As an aside, all the packages required by HERMIT
compiled fine, so it doesn't seem to break any existing code. I've also
run the ghc validate script, with no extra unexpected errors.
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/7162#comment:2>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
_______________________________________________
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
