On 04/13/2012 10:49 PM, Ben Millwood wrote:
I'm pleased to announce my first genuinely original Hackage package:
notcpp-0.0.1!
http://hackage.haskell.org/package/notcpp
[...]
Why is it
> scopeLookup :: String -> Q Exp
with n bound to x :: T => @scopeLookup n@ evaluates to an Exp containing
@Just x@
, not
> scopeLookup :: String -> Q (Maybe Exp)
with n bound to x :: T => @scopeLookup n@ evaluates to Just (an Exp
containing @x@)
? Shouldn't n's being in scope be a compile time decision? That would
also make the "openState: runtime name resolution has its drawbacks
:/"[1] a compile time error.
-- Steffen
[1]
http://hackage.haskell.org/packages/archive/notcpp/0.0.1/doc/html/NotCPP-ScopeLookup.html
_______________________________________________
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe
