Portability | portable |
---|---|
Stability | experimental |
Maintainer | libraries@haskell.org |
Safe Haskell | Safe-Infered |
Language.Haskell.TH.Syntax
Description
Abstract syntax definitions for Template Haskell.
Synopsis
- class (Monad m, Applicative m) => Quasi m where
- badIO :: String -> IO a
- counter :: IORef Int
- newtype Q a = Q {}
- runQ :: Quasi m => Q a -> m a
- newName :: String -> Q Name
- report :: Bool -> String -> Q ()
- reportError :: String -> Q ()
- reportWarning :: String -> Q ()
- recover :: Q a -> Q a -> Q a
- lookupName :: Bool -> String -> Q (Maybe Name)
- lookupTypeName :: String -> Q (Maybe Name)
- lookupValueName :: String -> Q (Maybe Name)
- reify :: Name -> Q Info
- reifyInstances :: Name -> [Type] -> Q [InstanceDec]
- isInstance :: Name -> [Type] -> Q Bool
- location :: Q Loc
- runIO :: IO a -> Q a
- addDependentFile :: FilePath -> Q ()
- returnQ :: a -> Q a
- bindQ :: Q a -> (a -> Q b) -> Q b
- sequenceQ :: [Q a] -> Q [a]
- class Lift t where
- liftString :: String -> Q Exp
- trueName, falseName :: Name
- nothingName, justName :: Name
- leftName, rightName :: Name
- newtype ModName = ModName String
- newtype PkgName = PkgName String
- newtype OccName = OccName String
- mkModName :: String -> ModName
- modString :: ModName -> String
- mkPkgName :: String -> PkgName
- pkgString :: PkgName -> String
- mkOccName :: String -> OccName
- occString :: OccName -> String
- data Name = Name OccName NameFlavour
- data NameFlavour
- con_NameS, con_NameG, con_NameL, con_NameU, con_NameQ :: Constr
- ty_NameFlavour :: DataType
- data NameSpace
- type Uniq = Int
- nameBase :: Name -> String
- nameModule :: Name -> Maybe String
- mkName :: String -> Name
- mkNameU :: String -> Uniq -> Name
- mkNameL :: String -> Uniq -> Name
- mkNameG :: NameSpace -> String -> String -> String -> Name
- mkNameG_v, mkNameG_d, mkNameG_tc :: String -> String -> String -> Name
- data NameIs
- showName :: Name -> String
- showName' :: NameIs -> Name -> String
- tupleDataName :: Int -> Name
- tupleTypeName :: Int -> Name
- mk_tup_name :: Int -> NameSpace -> Name
- unboxedTupleDataName :: Int -> Name
- unboxedTupleTypeName :: Int -> Name
- mk_unboxed_tup_name :: Int -> NameSpace -> Name
- data Loc = Loc {
- loc_filename :: String
- loc_package :: String
- loc_module :: String
- loc_start :: CharPos
- loc_end :: CharPos
- type CharPos = (Int, Int)
- data Info
- type ParentName = Name
- type Arity = Int
- type Unlifted = Bool
- type InstanceDec = Dec
- data Fixity = Fixity Int FixityDirection
- data FixityDirection
- maxPrecedence :: Int
- defaultFixity :: Fixity
- data Lit
- data Pat
- type FieldPat = (Name, Pat)
- data Match = Match Pat Body [Dec]
- data Clause = Clause [Pat] Body [Dec]
- data Exp
- = VarE Name
- | ConE Name
- | LitE Lit
- | AppE Exp Exp
- | InfixE (Maybe Exp) Exp (Maybe Exp)
- | UInfixE Exp Exp Exp
- | ParensE Exp
- | LamE [Pat] Exp
- | LamCaseE [Match]
- | TupE [Exp]
- | UnboxedTupE [Exp]
- | CondE Exp Exp Exp
- | MultiIfE [(Guard, Exp)]
- | LetE [Dec] Exp
- | CaseE Exp [Match]
- | DoE [Stmt]
- | CompE [Stmt]
- | ArithSeqE Range
- | ListE [Exp]
- | SigE Exp Type
- | RecConE Name [FieldExp]
- | RecUpdE Exp [FieldExp]
- type FieldExp = (Name, Exp)
- data Body
- data Guard
- data Stmt
- data Range
- data Dec
- = FunD Name [Clause]
- | ValD Pat Body [Dec]
- | DataD Cxt Name [TyVarBndr] [Con] [Name]
- | NewtypeD Cxt Name [TyVarBndr] Con [Name]
- | TySynD Name [TyVarBndr] Type
- | ClassD Cxt Name [TyVarBndr] [FunDep] [Dec]
- | InstanceD Cxt Type [Dec]
- | SigD Name Type
- | ForeignD Foreign
- | InfixD Fixity Name
- | PragmaD Pragma
- | FamilyD FamFlavour Name [TyVarBndr] (Maybe Kind)
- | DataInstD Cxt Name [Type] [Con] [Name]
- | NewtypeInstD Cxt Name [Type] Con [Name]
- | TySynInstD Name [Type] Type
- data FunDep = FunDep [Name] [Name]
- data FamFlavour
- data Foreign
- data Callconv
- data Safety
- = Unsafe
- | Safe
- | Interruptible
- data Pragma
- data Inline
- data RuleMatch
- data Phases
- = AllPhases
- | FromPhase Int
- | BeforePhase Int
- data RuleBndr
- = RuleVar Name
- | TypedRuleVar Name Type
- type Cxt = [Pred]
- data Pred
- data Strict
- data Con
- = NormalC Name [StrictType]
- | RecC Name [VarStrictType]
- | InfixC StrictType Name StrictType
- | ForallC [TyVarBndr] Cxt Con
- type StrictType = (Strict, Type)
- type VarStrictType = (Name, Strict, Type)
- data Type
- data TyVarBndr
- data TyLit
- type Kind = Type
- cmpEq :: Ordering -> Bool
- thenCmp :: Ordering -> Ordering -> Ordering
Documentation
class (Monad m, Applicative m) => Quasi m whereSource
Methods
Arguments
the error handler
action which may fail
Recover from the monadic fail
qLookupName :: Bool -> String -> m (Maybe Name)Source
qReify :: Name -> m Info Source
qReifyInstances :: Name -> [Type] -> m [Dec]Source
Input/output (dangerous)
qAddDependentFile :: FilePath -> m () Source
newName :: String -> Q Name Source
Generate a fresh name, which cannot be captured.
For example, this:
f = $(do nm1 <- newName "x" let nm2 =mkName
"x" return (LamE
[VarP
nm1] (LamE [VarP nm2] (VarE
nm1))) )
will produce the splice
f = \x0 -> \x -> x0
In particular, the occurrence VarE nm1
refers to the binding VarP nm1
,
and is not captured by the binding VarP nm2
.
Although names generated by newName
cannot be captured, they can
capture other names. For example, this:
g = $(do nm1 <- newName "x" let nm2 = mkName "x" return (LamE [VarP nm2] (LamE [VarP nm1] (VarE nm2))) )
will produce the splice
g = \x -> \x0 -> x0
since the occurrence VarE nm2
is captured by the innermost binding
of x
, namely VarP nm1
.
report :: Bool -> String -> Q () Source
Report an error (True) or warning (False),
but carry on; use fail
to stop.
reportError :: String -> Q () Source
Report an error to the user, but allow the current splice's computation to carry on. To abort the computation, use fail
.
reportWarning :: String -> Q () Source
Report a warning to the user, and carry on.
Recover from errors raised by reportError
or fail
.
lookupTypeName :: String -> Q (Maybe Name)Source
Look up the given name in the (type namespace of the) current splice's scope. See Language.Haskell.TH.Syntax for more details.
lookupValueName :: String -> Q (Maybe Name)Source
Look up the given name in the (value namespace of the) current splice's scope. See Language.Haskell.TH.Syntax for more details.
The functions lookupTypeName
and lookupValueName
provide
a way to query the current splice's context for what names
are in scope. The function lookupTypeName
queries the type
namespace, whereas lookupValueName
queries the value namespace,
but the functions are otherwise identical.
A call lookupValueName s
will check if there is a value
with name s
in scope at the current splice's location. If
there is, the Name
of this value is returned;
if not, then Nothing
is returned.
The returned name cannot be "captured". For example:
f = "global" g = $( do Just nm <- lookupValueName "f" [| let f = "local" in $( varE nm ) |]
In this case, g = "global"
; the call to lookupValueName
returned the global f
, and this name was not captured by
the local definition of f
.
The lookup is performed in the context of the top-level splice being run. For example:
f = "global" g = $( [| let f = "local" in $(do Just nm <- lookupValueName "f" varE nm ) |] )
Again in this example, g = "global"
, because the call to
lookupValueName
queries the context of the outer-most $(...)
.
Operators should be queried without any surrounding parentheses, like so:
lookupValueName "+"
Qualified names are also supported, like so:
lookupValueName "Prelude.+" lookupValueName "Prelude.map"
reify :: Name -> Q Info Source
reify
looks up information about the Name
.
It is sometimes useful to construct the argument name using lookupTypeName
or lookupValueName
to ensure that we are reifying from the right namespace. For instance, in this context:
data D = D
which D
does reify (mkName "D")
return information about? (Answer: D
-the-type, but don't rely on it.)
To ensure we get information about D
-the-value, use lookupValueName
:
do Just nm <- lookupValueName "D" reify nm
and to get information about D
-the-type, use lookupTypeName
.
reifyInstances :: Name -> [Type] -> Q [InstanceDec]Source
reifyInstances nm tys
returns a list of visible instances of nm tys
. That is,
if nm
is the name of a type class, then all instances of this class at the types tys
are returned. Alternatively, if nm
is the name of a data family or type family,
all instances of this family at the types tys
are returned.
isInstance :: Name -> [Type] -> Q Bool Source
Is the list of instances returned by reifyInstances
nonempty?
The runIO
function lets you run an I/O computation in the Q
monad.
Take care: you are guaranteed the ordering of calls to runIO
within
a single Q
computation, but not about the order in which splices are run.
Note: for various murky reasons, stdout and stderr handles are not necesarily flushed when the compiler finishes running, so you should flush them yourself.
addDependentFile :: FilePath -> Q () Source
Record external files that runIO is using (dependent upon). The compiler can then recognize that it should re-compile the file using this TH when the external file changes. Note that ghc -M will still not know about these dependencies - it does not execute TH. Expects an absolute file path.
Instances
liftString :: String -> Q Exp Source
Much of Name
API is concerned with the problem of name capture, which
can be seen in the following example.
f expr = [| let x = 0 in $expr |] ... g x = $( f [| x |] ) h y = $( f [| y |] )
A naive desugaring of this would yield:
g x = let x = 0 in x h y = let x = 0 in y
All of a sudden, g
and h
have different meanings! In this case,
we say that the x
in the RHS of g
has been captured
by the binding of x
in f
.
What we actually want is for the x
in f
to be distinct from the
x
in g
, so we get the following desugaring:
g x = let x' = 0 in x h y = let x' = 0 in y
which avoids name capture as desired.
In the general case, we say that a Name
can be captured if
the thing it refers to can be changed by adding new declarations.
An abstract type representing names in the syntax tree.
Name
s can be constructed in several ways, which come with different
name-capture guarantees (see Language.Haskell.TH.Syntax for
an explanation of name capture):
- the built-in syntax
'f
and''T
can be used to construct names, The expression'f
gives aName
which refers to the valuef
currently in scope, and''T
gives aName
which refers to the typeT
currently in scope. These names can never be captured. -
lookupValueName
andlookupTypeName
are similar to'f
and''T
respectively, but theName
s are looked up at the point where the current splice is being run. These names can never be captured. -
newName
monadically generates a new name, which can never be captured. -
mkName
generates a capturable name.
Names constructed using newName
and mkName
may be used in bindings
(such as let x = ...
or x -> ...
), but names constructed using
lookupValueName
, lookupTypeName
, 'f
, ''T
may not.
Constructors
data NameFlavour Source
Constructors
An unqualified name; dynamically bound
Instances
Although the NameFlavour type is abstract, the Data instance is not. The reason for this is that currently we use Data to serialize values in annotations, and in order for that to work for Template Haskell names introduced via the 'x syntax we need gunfold on NameFlavour to work. Bleh!
The long term solution to this is to use the binary package for annotation serialization and then remove this instance. However, to do _that_ we need to wait on binary to become stable, since boot libraries cannot be upgraded seperately from GHC itself.
This instance cannot be derived automatically due to bug #2701
nameModule :: Name -> Maybe String Source
Module prefix of a name, if it exists
mkName :: String -> Name Source
Generate a capturable name. Occurrences of such names will be resolved according to the Haskell scoping rules at the occurrence site.
For example:
f = [| pi + $(varE (mkName "pi")) |] ... g = let pi = 3 in $f
In this case, g
is desugared to
g = Prelude.pi + 3
Note that mkName
may be used with qualified names:
mkName "Prelude.pi"
See also dyn
for a useful combinator. The above example could
be rewritten using dyn
as
f = [| pi + $(dyn "pi") |]
mkNameG :: NameSpace -> String -> String -> String -> Name Source
Used for 'x etc, but not available to the programmer
tupleDataName :: Int -> Name Source
Tuple data constructor
tupleTypeName :: Int -> Name Source
Tuple type constructor
mk_tup_name :: Int -> NameSpace -> Name Source
unboxedTupleDataName :: Int -> Name Source
Unboxed tuple data constructor
unboxedTupleTypeName :: Int -> Name Source
Unboxed tuple type constructor
mk_unboxed_tup_name :: Int -> NameSpace -> Name Source
Constructors
Fields
- loc_filename :: String
- loc_package :: String
- loc_module :: String
- loc_start :: CharPos
- loc_end :: CharPos
Constructors
A "plain" type constructor. "Fancier" type constructors are returned using PrimTyConI
or FamilyI
as appropriate
A "primitive" type constructor, which can't be expressed with a Dec
. Examples: (->)
, Int#
.
A "value" variable (as opposed to a type variable, see TyVarI
).
The Maybe Dec
field contains Just
the declaration which
defined the variable -- including the RHS of the declaration --
or else Nothing
, in the case where the RHS is unavailable to
the compiler. At present, this value is _always_ Nothing
:
returning the RHS has not yet been implemented because of
lack of interest.
type ParentName = Name Source
In PrimTyConI
, arity of the type constructor
In PrimTyConI
, is the type constructor unlifted?
type InstanceDec = Dec Source
InstanceDec
desribes a single instance of a class or type function.
It is just a Dec
, but guaranteed to be one of the following:
-
InstanceD
(with empty[
)Dec
] -
DataInstD
orNewtypeInstD
(with empty derived[
)Name
] -
TySynInstD
Constructors
data FixityDirection Source
Highest allowed operator precedence for Fixity
constructor (answer: 9)
defaultFixity :: Fixity Source
Default fixity: infixl 9
When implementing antiquotation for quasiquoters, one often wants to parse strings into expressions:
parse :: String -> Maybe Exp
But how should we parse a + b * c
? If we don't know the fixities of
+
and *
, we don't know whether to parse it as a + (b * c)
or (a
+ b) * c
.
In cases like this, use UInfixE
or UInfixP
, which stand for
"unresolved infix expression" and "unresolved infix pattern". When
the compiler is given a splice containing a tree of UInfixE
applications such as
UInfixE (UInfixE e1 op1 e2) op2 (UInfixE e3 op3 e4)
it will look up and the fixities of the relevant operators and reassociate the tree as necessary.
- trees will not be reassociated across
ParensE
orParensP
, which are of use for parsing expressions like
(a + b * c) + d * e
-
InfixE
andInfixP
expressions are never reassociated. - The
UInfixE
constructor doesn't support sections. Sections such as(a *)
have no ambiguity, soInfixE
suffices. For longer sections such as(a + b * c -)
, use anInfixE
constructor for the outer-most section, and useUInfixE
constructors for all other operators:
InfixE Just (UInfixE ...a + b * c...) op Nothing
Sections such as (a + b +)
and ((a + b) +)
should be rendered
into Exp
s differently:
(+ a + b) ---> InfixE Nothing + (Just $ UInfixE a + b) -- will result in a fixity error if (+) is left-infix (+ (a + b)) ---> InfixE Nothing + (Just $ ParensE $ UInfixE a + b) -- no fixity errors
- Quoted expressions such as
[| a * b + c |] :: Q Exp [p| a : b : c |] :: Q Pat
will never contain UInfixE
, UInfixP
, ParensE
, or ParensP
constructors.
Pattern in Haskell given in {}
Constructors
{ _ }
Constructors
data FamFlavour Source
Instances
Constructors
Constructors
type StrictType = (Strict, Type)Source
type VarStrictType = (Name, Strict, Type)Source
To avoid duplication between kinds and types, they
are defined to be the same. Naturally, you would never
have a type be StarT
and you would never have a kind
be SigT
, but many of the other constructors are shared.
Note that the kind Bool
is denoted with ConT
, not
PromotedT
. Similarly, tuple kinds are made with TupleT
,
not PromotedTupleT
.