4 ms·
Am I correct in understanding that this means you can only have a list of typed ASTs, or a list of not-yet-typed ASTs, but not a list with a mix? Obviously I u
by jez 3y ago
Am I correct in understanding that this means you can only have a list of typed ASTs, or a list of not-yet-typed ASTs, but not a list with a mix?
Obviously I understand that if this is the limitation, then there are ways to work around this, and it all depends on how annoying the workarounds are.
But I’m curious is there a trick that allows it. All the tricks I can think of involve boxing the the ASTs you’re about to store in the list (which then come with memory/performance hits), and I’d love to be proven wrong.
- jmgrosen 3y agoUse an existential type, usually called Some in Haskell: https://hackage.haskell.org/package/some-1.0.5/docs/Data-Some.html https://hackage.haskell.org/package/some-1.0.5/docs/Data-Som... The implementation of this type one has in their head (a GADT) adds a boxing overhead, but the actual implementation in this library uses a newtype. That way if you have a type Expr a, you can have a list type [Some Expr].
- rowanG077 3y agoYou could make an intermediate step that's only used during type checking which may have partial type information. Then after type checking you lock it down. You can even have HLists but then you are also pretty far along the Ivory tower. I don't think that's worth it.