You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a clear dependency between regular patterns, where XmlSyntax transforms into RegularPatterns which in turn transforms into vanilla Haskell. It would simplify the code greatly (in particular that for transforming away XmlSyntax in expressions) if these transformations were done in two separate passes.
Note that XmlSyntax only depends on RegularPatterns in practice if pattern matching over XML is used. For real-world uses of XmlSyntax, this is only very rarely the case. We could thus consider a more fine-grained model, where XmlSyntax enables XML expressions, and a new extension XmlPatterns (which depends on/implies both RegularPatterns and XmlSyntax) handles the pattern side.
The text was updated successfully, but these errors were encountered:
There is a clear dependency between regular patterns, where
XmlSyntax
transforms intoRegularPatterns
which in turn transforms into vanilla Haskell. It would simplify the code greatly (in particular that for transforming awayXmlSyntax
in expressions) if these transformations were done in two separate passes.Note that
XmlSyntax
only depends onRegularPatterns
in practice if pattern matching over XML is used. For real-world uses ofXmlSyntax
, this is only very rarely the case. We could thus consider a more fine-grained model, whereXmlSyntax
enables XML expressions, and a new extensionXmlPatterns
(which depends on/implies bothRegularPatterns
andXmlSyntax
) handles the pattern side.The text was updated successfully, but these errors were encountered: