ghc-lib-parser-0.20190423: The GHC API, decoupled from GHC versions

CoreUnfold

Synopsis

# Documentation

data Unfolding Source #

Records the unfolding of an identifier, which is approximately the form the identifier would have if we substituted its definition in for the identifier. This type should be treated as abstract everywhere except in CoreUnfold

Instances
 Source # Instance detailsDefined in PprCore Methods

UnfoldingGuidance says when unfolding should take place

Instances
 Source # Instance detailsDefined in CoreSyn Methods Source # Instance detailsDefined in PprCore Methods

There is no known Unfolding

Make an unfolding that may be used unsaturated (ug_unsat_ok = unSaturatedOk) and that is reported as having its manifest arity (the number of outer lambdas applications will resolve before doing any work).

Make an unfolding that will be used once the RHS has been saturated to the given arity.

Constructors

 TrivArg NonTrivArg ValueArg
Instances
 Source # Instance detailsDefined in CoreUnfold Methods

Sees if the unfolding is pretty certain to inline. If so, return a *stable* unfolding for it, that will always inline.

data CallCtxt Source #

Constructors

 BoringCtxt RhsCtxt DiscArgCtxt RuleArgCtxt ValAppCtxt CaseCtxt
Instances
 Source # Instance detailsDefined in CoreUnfold Methods

Returns Just ([b1..bp], dc, [t1..tk], [x1..xn]) if the argument expression is a *saturated* constructor application of the form let b1 in .. let bp in dc t1..tk x1 .. xn, where t1..tk are the *universally-quantified* type args of dc. Floats can also be (and most likely are) single-alternative case expressions. Why does exprIsConApp_maybe return floats? We may have to look through lets and cases to detect that we are in the presence of a data constructor wrapper. In this case, we need to return the lets and cases that we traversed. See Note [exprIsConApp_maybe on data constructors with wrappers]. Data constructor wrappers are unfolded late, but we really want to trigger case-of-known-constructor as early as possible. See also Note [Activation for data constructor wrappers] in MkId.

We also return the incoming InScopeSet, augmented with the binders from any [FloatBind] that we return