[GHC] #14296: Add `Lift Exp` instance to `Language.Haskell.TH.Syntax`

#14296: Add `Lift Exp` instance to `Language.Haskell.TH.Syntax`
-------------------------------------+-------------------------------------
Reporter: heisenbug | Owner: (none)
Type: feature | Status: new
request |
Priority: normal | Milestone:
Component: Template | Version: 8.2.1
Haskell |
Keywords: | Operating System: Unknown/Multiple
Architecture: | Type of failure: Poor/confusing
Unknown/Multiple | error message
Test Case: | Blocked By:
Blocking: | Related Tickets:
Differential Rev(s): | Wiki Page:
-------------------------------------+-------------------------------------
Being open-minded, I played around with TH quotations and encountered a
strange error message:
TyFamWitnesses.hs:106:40-71: error:
• No instance for (Lift Exp) arising from a use of ‘lift’
• In the expression: lift eqTypeRep
In the expression:
{{{
[| eqTypeRep (typeRep @Maybe) |]
pending(rn) [

#14296: Add `Lift Exp` instance to `Language.Haskell.TH.Syntax` -------------------------------------+------------------------------------- Reporter: heisenbug | Owner: (none) Type: feature request | Status: new Priority: normal | Milestone: Component: Template Haskell | Version: 8.2.1 Resolution: | Keywords: Operating System: Unknown/Multiple | Architecture: Type of failure: Poor/confusing | Unknown/Multiple error message | Test Case: Blocked By: | Blocking: Related Tickets: #14030 | Differential Rev(s): Wiki Page: | -------------------------------------+------------------------------------- Changes (by RyanGlScott): * related: => #14030 Comment: This is planned as part of a larger proposal to derive `Lift` instances for all data types in `template-haskell`. See #14030. -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/14296#comment:1 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler

#14296: Add `Lift Exp` instance to `Language.Haskell.TH.Syntax` -------------------------------------+------------------------------------- Reporter: heisenbug | Owner: (none) Type: feature request | Status: new Priority: normal | Milestone: Component: Template Haskell | Version: 8.2.1 Resolution: | Keywords: Operating System: Unknown/Multiple | Architecture: Type of failure: Poor/confusing | Unknown/Multiple error message | Test Case: Blocked By: | Blocking: Related Tickets: #14030 | Differential Rev(s): Wiki Page: | -------------------------------------+------------------------------------- Comment (by RyanGlScott): However, it should be noted that a derived `Lift` instance for `Exp` would not produce the code above. The problem with that instance is that if `x :: Exp`, then `$(lift x)` would not necessarily equal `x` (or even be of type `Exp`!), which is a rule you'd generally expect to hold. (I realize this law isn't started anywhere in the Haddocks at the moment, but it probably should be.) -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/14296#comment:2 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler

#14296: Add `Lift Exp` instance to `Language.Haskell.TH.Syntax` -------------------------------------+------------------------------------- Reporter: heisenbug | Owner: (none) Type: feature request | Status: new Priority: normal | Milestone: Component: Template Haskell | Version: 8.2.1 Resolution: | Keywords: Operating System: Unknown/Multiple | Architecture: Type of failure: Poor/confusing | Unknown/Multiple error message | Test Case: Blocked By: | Blocking: Related Tickets: #14030 | Differential Rev(s): Wiki Page: | -------------------------------------+------------------------------------- Comment (by heisenbug): Replying to [comment:2 RyanGlScott]:
However, it should be noted that a derived `Lift` instance for `Exp` would not produce the code above. The problem with that instance is that if `x :: Exp`, then `$(lift x)` would not necessarily equal `x` (or even be of type `Exp`!), which is a rule you'd generally expect to hold. (I realize this law isn't started anywhere in the Haddocks at the moment, but it probably should be.)
Interesting. I did not think about that too deeply. Maybe worth documenting this. But in my case (the specific usage in `[e|eqTypeRep (typeRep @ Maybe)|]`) the invariant is satisfied: `lift eqTypeRep` should encode an `Exp`. After all, I use it in this context `[p|($here -> Just HRefl)|]` as the view function. So I should be safe, right? Should I err, the type checker will remind me after quotation expansion, won't it? What about the derivation mechanism for `Lift` instances? Will it do ''the right thing'' in this case too? Anyway, thanks for the insight! -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/14296#comment:3 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler

#14296: Add `Lift Exp` instance to `Language.Haskell.TH.Syntax` -------------------------------------+------------------------------------- Reporter: heisenbug | Owner: (none) Type: feature request | Status: new Priority: normal | Milestone: Component: Template Haskell | Version: 8.2.1 Resolution: | Keywords: Operating System: Unknown/Multiple | Architecture: Type of failure: Poor/confusing | Unknown/Multiple error message | Test Case: Blocked By: | Blocking: Related Tickets: #14030 | Differential Rev(s): Wiki Page: | -------------------------------------+------------------------------------- Comment (by RyanGlScott): Let me try and articulate more precisely what this invariant is capturing. Here are some examples of the invariant at work: {{{#!hs {-# LANGUAGE TemplateHaskell #-} import Language.Haskell.TH.Syntax test :: IO () test = mapM_ print [ $(lift True) == True , $(lift "hello") == "hello" ] }}} These should all print `True`, and more generally, you should be able to stick in any other `Bool` or `String` and also have it print all `True`s. But it's easy to subvert this with your proposed `Lift Exp` instance, since you can have, e.g.: {{{#!hs uhOh :: Exp uhOh = lift "uhOh" }}} Now `$(lift uhOh)` won't be an `Exp`, but rather a `String`. This is not at all what we want. Replying to [comment:3 heisenbug]:
What about the derivation mechanism for `Lift` instances? Will it do ''the right thing'' in this case too?
Right. Here is an except of the `-ddump-deriv` output from deriving a `Lift` instance for `Exp`: {{{#!hs deriving instance Lift Exp ===> instance Lift Exp where lift (VarE a) = conE 'VarE `appE` lift a lift (ConE a) = conE 'ConE `appE` lift a lift (AppE f x) = conE 'AppE `appE` lift f `appE` lift x ... }}} Now calling `lift` on an `Exp` will produce an `ExpQ` that represents an `Exp` value. It's quite meta, granted, but that's how it should be :) In any case, I've been meaning to resolve #14030 for a while now, but haven't had much time to look into it recently. One obstacle is that deriving `Lift` instances for data types in `template-haskell` during stage-1 compilation is harder than it sounds because GHC HEAD moved around the locations of functions that are used when deriving `Lift` instances themselves. Therefore, I think I'll have to disable generating `Lift` instances on stage-1 compilers for now to make it work, but I've yet to figure out how to accomplish that. -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/14296#comment:4 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler

#14296: Add `Lift Exp` instance to `Language.Haskell.TH.Syntax` -------------------------------------+------------------------------------- Reporter: heisenbug | Owner: (none) Type: feature request | Status: new Priority: normal | Milestone: Component: Template Haskell | Version: 8.2.1 Resolution: | Keywords: Operating System: Unknown/Multiple | Architecture: Type of failure: Poor/confusing | Unknown/Multiple error message | Test Case: Blocked By: | Blocking: Related Tickets: #14030 | Differential Rev(s): Wiki Page: | -------------------------------------+------------------------------------- Comment (by heisenbug): Replying to [comment:4 RyanGlScott]:
<SNIP>
But it's easy to subvert this with your proposed `Lift Exp` instance, since you can have, e.g.:
{{{#!hs uhOh :: Exp uhOh = lift "uhOh" }}}
You mean {{{#!hs uhOh :: ExpQ uhOh = lift "uhOh" }}}
Now `$(lift uhOh)` won't be an `Exp`, but rather a `String`. This is not at all what we want.
Totally agree. My question is when this happens in a `[p|($uhOh -> binding)|]` and this ends up in a splice, ultimately being compiled by GHC, then I'll get a type error "Expected `Exp`, got: `String`", correct?
Replying to [comment:3 heisenbug]:
What about the derivation mechanism for `Lift` instances? Will it do
''the right thing'' in this case too?
Right. Here is an except of the `-ddump-deriv` output from deriving a
`Lift` instance for `Exp`:
{{{#!hs deriving instance Lift Exp
===>
instance Lift Exp where lift (VarE a) = conE 'VarE `appE` lift a lift (ConE a) = conE 'ConE `appE` lift a lift (AppE f x) = conE 'AppE `appE` lift f `appE` lift x ... }}}
Now calling `lift` on an `Exp` will produce an `ExpQ` that represents an
`Exp` value. It's quite meta, granted, but that's how it should be :) That's good. Thanks! -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/14296#comment:5 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler

#14296: Add `Lift Exp` instance to `Language.Haskell.TH.Syntax` -------------------------------------+------------------------------------- Reporter: heisenbug | Owner: (none) Type: feature request | Status: new Priority: normal | Milestone: Component: Template Haskell | Version: 8.2.1 Resolution: | Keywords: Operating System: Unknown/Multiple | Architecture: Type of failure: Poor/confusing | Unknown/Multiple error message | Test Case: Blocked By: | Blocking: Related Tickets: #14030 | Differential Rev(s): Wiki Page: | -------------------------------------+------------------------------------- Comment (by RyanGlScott): Replying to [comment:5 heisenbug]:
You mean {{{#!hs uhOh :: ExpQ uhOh = lift "uhOh" }}}
Oops. That's right.
My question is when this happens in a `[p|($uhOh -> binding)|]` and this ends up in a splice, ultimately being compiled by GHC, then I'll get a type error "Expected `Exp`, got: `String`", correct?
Sure, GHC will definitely catch the mistake in the form of a (sometimes hard-to-scrutinize) type error. But I would still be frustrated that that happened in the first place, since it would violate my intuition of how `lift` interacts with splicing. -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/14296#comment:6 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler

#14296: Add `Lift Exp` instance to `Language.Haskell.TH.Syntax` -------------------------------------+------------------------------------- Reporter: heisenbug | Owner: (none) Type: feature request | Status: closed Priority: normal | Milestone: Component: Template Haskell | Version: 8.2.1 Resolution: duplicate | Keywords: Operating System: Unknown/Multiple | Architecture: Type of failure: Poor/confusing | Unknown/Multiple error message | Test Case: Blocked By: | Blocking: Related Tickets: #14030 | Differential Rev(s): Wiki Page: | -------------------------------------+------------------------------------- Changes (by RyanGlScott): * status: new => closed * resolution: => duplicate Comment: I've added a Diff for documenting this `Lift` law in Phab:D4050. Since we seem to both be in agreement that deriving `Lift` for `Exp` is the better way to go, I'll close this in favor of #14030. -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/14296#comment:7 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler

#14296: Add `Lift Exp` instance to `Language.Haskell.TH.Syntax`
-------------------------------------+-------------------------------------
Reporter: heisenbug | Owner: (none)
Type: feature request | Status: closed
Priority: normal | Milestone:
Component: Template Haskell | Version: 8.2.1
Resolution: duplicate | Keywords:
Operating System: Unknown/Multiple | Architecture:
Type of failure: Poor/confusing | Unknown/Multiple
error message | Test Case:
Blocked By: | Blocking:
Related Tickets: #14030 | Differential Rev(s):
Wiki Page: |
-------------------------------------+-------------------------------------
Comment (by Ben Gamari
participants (1)
-
GHC