RE: Why is EvTerm limited?

| What would break if we had
|
| | EvExpr CoreExpr
|
| as an additional constructor there?
This has come up before. I think that'd be a solid win.
In fact, eliminate all the existing evidence constructors with "smart constructors" that produce an EvExpr. That'd mean moving stuff from the desugarer into these smart constructors, but that's ok.
I /think/ I didn't do that initially only because there were very few forms and it mean that there was no CoreExpr stuff in the type checker. But as we add more forms that decision looks and less good.
You'd need to add zonkCoreExpr in place of zonkEvTerm.
evVarsOfTerm is called quite a bit; you might want to cache the result in the EvExpr constructor.
Make a ticket and execute?
Simon
| -----Original Message-----
| From: Glasgow-haskell-users [mailto:glasgow-haskell-users-
| bounces@haskell.org] On Behalf Of Joachim Breitner
| Sent: 19 January 2018 14:01
| To: Glasgow-Haskell-Users users
participants (1)
-
Simon Peyton Jones