Safe Haskell | None |
---|---|
Language | Haskell2010 |
- * *
GREInfo
* *
************************************************************************
Note [GREInfo]
~~~~~~~~~~~~~~
In the renamer, we sometimes need a bit more information about a
Name
, e.g. whether it is a type constructor, class, data constructor, record field, etc. For example, when typechecking record construction, the renamer needs to look up the fields of the data constructor being used (see e.g. GHC.Rename.Pat.rnHsRecFields). Extra information also allows us to provide better error messages when a fatal error occurs in the renamer, as it allows us to distinguish classes, type families, type synonyms, etc. For imported Names, we have access to the full type information in the form of a TyThing (although see Note [Retrieving the GREInfo from interfaces]). However, for Names in the module currently being renamed, we don't yet have full information. Instead of using TyThing, we use the GREInfo type, and this information gets affixed to each element in the GlobalRdrEnv. This allows us to treat imported and local Names in a consistent manner: always look at the GREInfo. Note [Retrieving the GREInfo from interfaces] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ If we have a TyThing, we can easily compute the corresponding GREInfo: this is done in GHC.Types.TyThing.tyThingGREInfo. However, one often needs to produce GlobalRdrElts (and thus their GREInfos) directly after loading interface files, before they are typechecked. For example: - GHC.Tc.Module.tcRnModuleTcRnM first calls tcRnImports, which starts off calling rnImports which transitively calls filterImports. That function is responsible for coughing up GlobalRdrElts (and their GREInfos) obtained from interfaces, but we will only typecheck the interfaces after we have finished processing the imports (see e.g. the logic at the start of tcRnImports which sets eps_is_boot, which decides whether we should look in the boot or non-boot interface for any particular module). - GHC.Tc.Utils.Backpack.mergeSignatures first loads the relevant signature interfaces to merge them, but only later on does it typecheck them. In both of these examples, what's important is that we **lazily** produce the GREInfo: it should only be consulted once the interfaces have been typechecked, which will add the necessary information to the type-level environment. In particular, the respective functionsfilterImports
andmergeSignatures
should NOT force the gre_info field. We delay the loading of interfaces by making the gre_info field ofGlobalRdrElt
a thunk which, when forced, loads the interface, looks up theName
in the type environment to get its associated TyThing, and computes the GREInfo from that. SeelookupGREInfo
. A possible alternative design would be to change the AvailInfo datatype to also store GREInfo. We currently don't do that, as this would mean that every time an interface re-exports something it has to also provide its GREInfo, which could lead to bloat. Note [Forcing GREInfo] ~~~~~~~~~~~~~~~~~~~~~~ The GREInfo field of a GlobalRdrElt needs to be lazy, as explained in Note [Retrieving the GREInfo from interfaces]. For imported things, this field is usually a thunk which looks up the GREInfo in a type environment (see GHC.Rename.Env.lookupGREInfo). We thus need to be careful not to introduce space leaks: such thunks could end up retaining old type environments, which would violate invariant (5) of Note [GHC Heap Invariants] in GHC.Driver.Make. This can happen, for example, when reloading in GHCi (see e.g. test T15369, which can trigger the ghci leak check if we're not careful). A naive approach is to simply deeply force the whole GlobalRdrEnv. However, forcing the GREInfo thunks can force the loading of interface files which we otherwise might not need to load, so it leads to wasted work. Instead, whenever we are about to store the GlobalRdrEnv somewhere (such as in ModDetails), we dehydrate it by stripping away the GREInfo field, turning it into (). SeeforceGlobalRdrEnv
and its cousinhydrateGlobalRdrEnv
, as well as Note [IfGlobalRdrEnv] in GHC.Types.Name.Reader. Search for references to this note in the code for illustration. - * *
Constructor info
* *
************************************************************************
Note [Local constructor info in the renamer]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
As explained in Note [GREInfo], information pertinent to the renamer is
stored using the GREInfo datatype. What information do we need about constructors?
Consider the following example:
data T = T1 { x, y :: Int }
| T2 { x :: Int }
| T3
| T4 Int Bool
We need to know:
* The fields of the data constructor, so that
- We can complain if you say `T1 { v = 3 }`, where
v
is not a field ofT1
See the following call stack * GHC.Rename.Expr.rnExpr (RecordCon case) * GHC.Rename.Pat.rnHsRecFields * GHC.Rename.Env.lookupRecFieldOcc - Ditto if you pattern match on `T1 { v = x }`. See the following call stack * GHC.Rename.Pat.rnHsRecPatsAndThen * GHC.Rename.Pat.rnHsRecFields * GHC.Rename.Env.lookupRecFieldOcc - We can fill in the dots if you say `T1 {..}` in construction or pattern matching See GHC.Rename.Pat.rnHsRecFields.rn_dotdot * Whether the contructor is nullary. We need to know this to accept `T2 {..}`, and `T3 {..}`, but reject `T4 {..}`, in both construction and pattern matching. See GHC.Rename.Pat.rnHsRecFields.rn_dotdot and Note [Nullary constructors and empty record wildcards] Note [Nullary constructors and empty record wildcards] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ A nullary constructor is one with no arguments. For example, both `data T = MkT` and `data T = MkT {}` are nullary. For consistency and TH convenience, it was agreed that a `{..}` match or usage on nullary constructors would be accepted. This is done as as per https://github.com/ghc-proposals/ghc-proposals/blob/master/proposals/0496-empty-record-wildcards.rst - * * Record field info * * **********************************************************************
Renamer-level information about Name
s.
Renamer equivalent of TyThing
.
Synopsis
- data GREInfo
- plusGREInfo :: GREInfo -> GREInfo -> GREInfo
- data ConInfo
- mkConInfo :: Arity -> [FieldLabel] -> ConInfo
- conInfoFields :: ConInfo -> [FieldLabel]
- data ConLikeName
- = DataConName {
- conLikeName_Name :: !Name
- | PatSynName {
- conLikeName_Name :: !Name
- = DataConName {
- data RecFieldInfo = RecFieldInfo {}
* *
GREInfo
* *
************************************************************************
Note [GREInfo]
~~~~~~~~~~~~~~
In the renamer, we sometimes need a bit more information about a Name
, e.g.
whether it is a type constructor, class, data constructor, record field, etc.
For example, when typechecking record construction, the renamer needs to look
up the fields of the data constructor being used (see e.g. GHC.Rename.Pat.rnHsRecFields).
Extra information also allows us to provide better error messages when a fatal
error occurs in the renamer, as it allows us to distinguish classes, type families,
type synonyms, etc.
For imported Names, we have access to the full type information in the form of
a TyThing (although see Note [Retrieving the GREInfo from interfaces]).
However, for Names in the module currently being renamed, we don't
yet have full information. Instead of using TyThing, we use the GREInfo type,
and this information gets affixed to each element in the GlobalRdrEnv.
This allows us to treat imported and local Names in a consistent manner:
always look at the GREInfo.
Note [Retrieving the GREInfo from interfaces]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If we have a TyThing, we can easily compute the corresponding GREInfo: this is
done in GHC.Types.TyThing.tyThingGREInfo.
However, one often needs to produce GlobalRdrElts (and thus their GREInfos)
directly after loading interface files, before they are typechecked. For example:
- GHC.Tc.Module.tcRnModuleTcRnM first calls tcRnImports, which starts off
calling rnImports which transitively calls filterImports. That function
is responsible for coughing up GlobalRdrElts (and their GREInfos) obtained
from interfaces, but we will only typecheck the interfaces after we have
finished processing the imports (see e.g. the logic at the start of tcRnImports
which sets eps_is_boot, which decides whether we should look in the boot
or non-boot interface for any particular module).
- GHC.Tc.Utils.Backpack.mergeSignatures first loads the relevant signature
interfaces to merge them, but only later on does it typecheck them.
In both of these examples, what's important is that we **lazily** produce the
GREInfo: it should only be consulted once the interfaces have been typechecked,
which will add the necessary information to the type-level environment.
In particular, the respective functions filterImports
and mergeSignatures
should NOT force the gre_info field.
We delay the loading of interfaces by making the gre_info field of GlobalRdrElt
a thunk which, when forced, loads the interface, looks up the Name
in the type
environment to get its associated TyThing, and computes the GREInfo from that.
See lookupGREInfo
.
A possible alternative design would be to change the AvailInfo datatype to also
store GREInfo. We currently don't do that, as this would mean that every time
an interface re-exports something it has to also provide its GREInfo, which
could lead to bloat.
Note [Forcing GREInfo]
~~~~~~~~~~~~~~~~~~~~~~
The GREInfo field of a GlobalRdrElt needs to be lazy, as explained in
Note [Retrieving the GREInfo from interfaces]. For imported things, this field
is usually a thunk which looks up the GREInfo in a type environment
(see GHC.Rename.Env.lookupGREInfo).
We thus need to be careful not to introduce space leaks: such thunks could end
up retaining old type environments, which would violate invariant (5) of
Note [GHC Heap Invariants] in GHC.Driver.Make. This can happen, for example,
when reloading in GHCi (see e.g. test T15369, which can trigger the ghci leak check
if we're not careful).
A naive approach is to simply deeply force the whole GlobalRdrEnv. However,
forcing the GREInfo thunks can force the loading of interface files which we
otherwise might not need to load, so it leads to wasted work.
Instead, whenever we are about to store the GlobalRdrEnv somewhere (such as
in ModDetails), we dehydrate it by stripping away the GREInfo field, turning it
into (). See forceGlobalRdrEnv
and its cousin hydrateGlobalRdrEnv
,
as well as Note [IfGlobalRdrEnv] in GHC.Types.Name.Reader.
Search for references to this note in the code for illustration.
Information about a Name
that is pertinent to the renamer.
See Note [GREInfo]
Vanilla | No particular information... e.g. a function |
UnboundGRE | An unbound GRE... could be anything |
IAmTyCon !(TyConFlavour Name) |
|
IAmConLike | |
| |
IAmRecField !RecFieldInfo |
Instances
Data GREInfo Source # | |
Defined in GHC.Types.GREInfo gfoldl :: (forall d b. Data d => c (d -> b) -> d -> c b) -> (forall g. g -> c g) -> GREInfo -> c GREInfo Source # gunfold :: (forall b r. Data b => c (b -> r) -> c r) -> (forall r. r -> c r) -> Constr -> c GREInfo Source # toConstr :: GREInfo -> Constr Source # dataTypeOf :: GREInfo -> DataType Source # dataCast1 :: Typeable t => (forall d. Data d => c (t d)) -> Maybe (c GREInfo) Source # dataCast2 :: Typeable t => (forall d e. (Data d, Data e) => c (t d e)) -> Maybe (c GREInfo) Source # gmapT :: (forall b. Data b => b -> b) -> GREInfo -> GREInfo Source # gmapQl :: (r -> r' -> r) -> r -> (forall d. Data d => d -> r') -> GREInfo -> r Source # gmapQr :: forall r r'. (r' -> r -> r) -> r -> (forall d. Data d => d -> r') -> GREInfo -> r Source # gmapQ :: (forall d. Data d => d -> u) -> GREInfo -> [u] Source # gmapQi :: Int -> (forall d. Data d => d -> u) -> GREInfo -> u Source # gmapM :: Monad m => (forall d. Data d => d -> m d) -> GREInfo -> m GREInfo Source # gmapMp :: MonadPlus m => (forall d. Data d => d -> m d) -> GREInfo -> m GREInfo Source # gmapMo :: MonadPlus m => (forall d. Data d => d -> m d) -> GREInfo -> m GREInfo Source # | |
NFData GREInfo Source # | |
Defined in GHC.Types.GREInfo | |
Outputable GREInfo Source # | |
* *
Constructor info
* *
************************************************************************
Note [Local constructor info in the renamer]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
As explained in Note [GREInfo], information pertinent to the renamer is
stored using the GREInfo datatype. What information do we need about constructors?
Consider the following example:
data T = T1 { x, y :: Int }
| T2 { x :: Int }
| T3
| T4 Int Bool
We need to know:
* The fields of the data constructor, so that
- We can complain if you say `T1 { v = 3 }`, where v
is not a field of T1
See the following call stack
* GHC.Rename.Expr.rnExpr (RecordCon case)
* GHC.Rename.Pat.rnHsRecFields
* GHC.Rename.Env.lookupRecFieldOcc
- Ditto if you pattern match on `T1 { v = x }`.
See the following call stack
* GHC.Rename.Pat.rnHsRecPatsAndThen
* GHC.Rename.Pat.rnHsRecFields
* GHC.Rename.Env.lookupRecFieldOcc
- We can fill in the dots if you say `T1 {..}` in construction or pattern matching
See GHC.Rename.Pat.rnHsRecFields.rn_dotdot
* Whether the contructor is nullary.
We need to know this to accept `T2 {..}`, and `T3 {..}`, but reject `T4 {..}`,
in both construction and pattern matching.
See GHC.Rename.Pat.rnHsRecFields.rn_dotdot
and Note [Nullary constructors and empty record wildcards]
Note [Nullary constructors and empty record wildcards]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
A nullary constructor is one with no arguments.
For example, both `data T = MkT` and `data T = MkT {}` are nullary.
For consistency and TH convenience, it was agreed that a `{..}`
match or usage on nullary constructors would be accepted.
This is done as as per https://github.com/ghc-proposals/ghc-proposals/blob/master/proposals/0496-empty-record-wildcards.rst
Information about the record fields of a constructor.
See Note [Local constructor info in the renamer]
Instances
Data ConInfo Source # | |
Defined in GHC.Types.GREInfo gfoldl :: (forall d b. Data d => c (d -> b) -> d -> c b) -> (forall g. g -> c g) -> ConInfo -> c ConInfo Source # gunfold :: (forall b r. Data b => c (b -> r) -> c r) -> (forall r. r -> c r) -> Constr -> c ConInfo Source # toConstr :: ConInfo -> Constr Source # dataTypeOf :: ConInfo -> DataType Source # dataCast1 :: Typeable t => (forall d. Data d => c (t d)) -> Maybe (c ConInfo) Source # dataCast2 :: Typeable t => (forall d e. (Data d, Data e) => c (t d e)) -> Maybe (c ConInfo) Source # gmapT :: (forall b. Data b => b -> b) -> ConInfo -> ConInfo Source # gmapQl :: (r -> r' -> r) -> r -> (forall d. Data d => d -> r') -> ConInfo -> r Source # gmapQr :: forall r r'. (r' -> r -> r) -> r -> (forall d. Data d => d -> r') -> ConInfo -> r Source # gmapQ :: (forall d. Data d => d -> u) -> ConInfo -> [u] Source # gmapQi :: Int -> (forall d. Data d => d -> u) -> ConInfo -> u Source # gmapM :: Monad m => (forall d. Data d => d -> m d) -> ConInfo -> m ConInfo Source # gmapMp :: MonadPlus m => (forall d. Data d => d -> m d) -> ConInfo -> m ConInfo Source # gmapMo :: MonadPlus m => (forall d. Data d => d -> m d) -> ConInfo -> m ConInfo Source # | |
NFData ConInfo Source # | |
Defined in GHC.Types.GREInfo | |
Outputable ConInfo Source # | |
Eq ConInfo Source # | |
conInfoFields :: ConInfo -> [FieldLabel] Source #
data ConLikeName Source #
Useful when we are in the renamer and don't yet have a full DataCon
or
PatSyn
to hand.
Instances
* * Record field info * * **********************************************************************
data RecFieldInfo Source #
RecFieldInfo | |
|