[GHC] #10047: inconsistency in name binding between splice and quasiquotation
GHC
ghc-devs at haskell.org
Sun Jun 7 02:40:08 UTC 2015
#10047: inconsistency in name binding between splice and quasiquotation
-------------------------------------+-------------------------------------
Reporter: rwbarton | Owner:
Type: bug | Status: new
Priority: normal | Milestone: 7.12.1
Component: Template Haskell | Version: 7.8.4
Resolution: | Keywords:
Operating System: Unknown/Multiple | Architecture:
Type of failure: None/Unknown | Unknown/Multiple
Blocked By: | Test Case: th/T10047
Related Tickets: | Blocking:
| Differential Revisions:
-------------------------------------+-------------------------------------
Comment (by spinda):
re: what multiple declaration splices would see in their reification
environments, the current behavior for quasiquoters seems to be to
evaluate declaration quasiquoters in the order of appearance in the
source. So decalarations produced by a declaration splice further up the
file would make it into the reification environments of subsequent
declaration splices. Declarations produced by splices lower down would be
invisible to ones further up. This seems reasonable to me, as long as the
scoping restriction is contained within the TH/quasiquoter processing and
doesn't leak out over the rest of the source.
I'm likely overlooking a deeper issue here, so please let me know what
else would need to be addressed.
re: anti-quotation in quasiquoters, I think I misunderstood simonpj's
comment the first time around. If I understand correctly now, this isn't
referring to some new native support for antiquotation, but rather an
example of how a quasiquoter would come to use {{{reify}}}.
--
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/10047#comment:12>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
More information about the ghc-tickets
mailing list