Skip to content

Changes

Page history
Edit RecordPatternMatching authored by malcolm.wallace@cs.york.ac.uk's avatar malcolm.wallace@cs.york.ac.uk
Hide whitespace changes
Inline Side-by-side
record-pattern-matching.md
View page @ e02a5c0a
...@@ -9,3 +9,6 @@ There are two possible ways forward: ...@@ -9,3 +9,6 @@ There are two possible ways forward:
- Clarify the description to ratify GHC's behaviour, i.e. record fields are matched in the order written in the **datatype**. Pros: this is easier to implement, Cons: it is not quite as intuitive for the programmer. - Clarify the description to ratify GHC's behaviour, i.e. record fields are matched in the order written in the **datatype**. Pros: this is easier to implement, Cons: it is not quite as intuitive for the programmer.
- Clarify the description to specify that fields are matched in the order written in the pattern. - Clarify the description to specify that fields are matched in the order written in the pattern.
The [ errata list for the Revised H'98 Report](http://www.haskell.org/definition/haskell98-revised-bugs.html) resolved this issue (after discussion on the haskell mailing list), in favour of the second option - i.e. the pattern order, not the declaration order.