From acaa6e12450b2de3a14f630a11f736a9b7092094 Mon Sep 17 00:00:00 2001 From: simonpj Date: Mon, 16 Aug 1999 15:53:50 +0000 Subject: [PATCH] [project @ 1999-08-16 15:53:50 by simonpj] Add note about exports of RULES --- ghc/docs/users_guide/glasgow_exts.vsgml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/ghc/docs/users_guide/glasgow_exts.vsgml b/ghc/docs/users_guide/glasgow_exts.vsgml index dc7c413..ce0fc91 100644 --- a/ghc/docs/users_guide/glasgow_exts.vsgml +++ b/ghc/docs/users_guide/glasgow_exts.vsgml @@ -1,5 +1,5 @@ % -% $Id: glasgow_exts.vsgml,v 1.13 1999/08/02 09:52:43 simonmar Exp $ +% $Id: glasgow_exts.vsgml,v 1.14 1999/08/16 15:53:50 simonpj Exp $ % % GHC Language Extensions. % @@ -2120,6 +2120,12 @@ because @wibble@ will be inlined (it's small). Later on in compilation, GHC starts inlining even things on the LHS of rules, but still leaves the rules enabled. This inlining policy is controlled by the per-simplification-pass flag @-finline-phase@n. + + All rules are implicitly exported from the module, and are therefore +in force in any module that imports the module that defined the rule, directly +or indirectly. (That is, if A imports B, which imports C, then C's rules are +in force when compiling A.) The situation is very like that for instance +declarations. -- 1.7.10.4