With the help of Jan Stolarek I tracked down the HsForAllTy flattening to `HsTypes.mk_forall_ty`.
This function takes any nested HsForAllTy's where the top one does not have a context defined, and collapses them into a single one. I do not know what the motivation for this is, and if it perhaps speeds up or simplifies further compilation. But now that API Annotations have arrived, making sure we do not lose the annotations for the sub-HsForAllTy causes significant gymnastics in the parser [1]. So my question is, is there a good reason to continue doing this, given the trade-off in parser complexity. Regards Alan [1] https://phabricator.haskell.org/D833
_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
