|Version 2 (modified by augustss, 3 years ago) (diff)|
Most language entities in Haskell can be named so that they can be abbreviated instead of written out in full. This proposal provides the same power for patterns.
Here is a simple representation of types
data Type = App String [Type]
Using this representations the arrow type looks like App "->" [t1, t2]. Here are functions to collect are all argument types of nested arrows and recognizing the Int type:
collectArgs :: Type -> [Type] collectArgs (App "->" [t1, t2]) = t1 : collectArgs t2 collectArgs _ =  isInt (App "Int" ) = True isInt _ = False
Matching on the arrow type is both hard to read and error prone to write.
The proposal is to introduce a way to give pattern names:
pattern Arrow t1 t2 = App "->" [t1, t2] pattern Int = App "Int" 
And now we can write
collectArgs :: Type -> [Type] collectArgs (Arrow t1 t2) = t1 : collectArgs t2 collectArgs _ =  isInt Int = True isInt _ = False
Furthermore, the pattern synonym can also be used in expressions, e.g.,
arrows :: [Type] -> Type -> Type arrows = foldr Arrow
Simple pattern synonyms
The simplest form of pattern synonyms is the one from the examples above. The grammar rule is simply:
pattern conid varid1 ... varidn = patexp
where patexp is simply the intersection of the grammars for patterns and expression, i.e., those terms that are valid both as a pattern and as an expressions. Each of the variables on the left hand side must occur exactly one on the right hand side, and these are the only variables that can be mention on the right hand side. The semantics is simply given by expansions of the synonym. Pattern synonyms are not allowed to be recursive. Cf. type synonyms.
Pattern synonyms can be exported and imported by mentioning the conid in the export/import list. Note that this suffers from the same constructor vs type confusion that already exists in hiding list, i.e., given the mention of a conid you cannot tell if it refers to a constructor or a type.
Pattern only synonyms
The simple patterns synonyms are restricted to having a right hand side that is also a valid expression. The pattern only synonyms can have any pattern on the right hand side, but may only be used in patterns.
pattern conid varid1 ... varidn ~ pat
Note the use of ~ instead of = as the equality symbol. This serves as a syntactic cue that this is a pattern only synonym. Again, each of the variables on the left hand side must be mentioned exactly once of the right hand side, but the right hand side can mention other variables as well. These variables will not be bound by using the pattern synonyms.
pattern ThirdElem x ~ _:_:x:_ pattern LazySecond a b ~ (a, ~b) third (ThirdElem a) = a third _ = error "No third" fcn :: (Int, (Int, Int)) fcn (LazySecond x (y, z)) = if x == 0 then 0 else y+z
And their expansions
third (_:_:a:_) = a third _ = error "No third" fcn :: (Int, (Int, Int)) fcn (x ~(y, z)) = if x == 0 then 0 else y+z