ghci -XNoTraditionalRecordSyntax does not complain of unsupported extensions for me.
The flag appears to just disable record construction and update syntax, and record patterns, and record syntax in GADT declarations. It has probably never been used.
Simon
| -----Original Message-----
| From: glasgow-haskell-users-bounces@haskell.org [mailto:glasgow-haskell-
| users-bounces@haskell.org] On Behalf Of AntC
| Sent: 26 March 2012 23:47
| To: glasgow-haskell-users@haskell.org
| Subject: Re: ANNOUNCE: GHC version 7.2.1 - {-# LANGUAGE
| NoTraditionalRecordSyntax #-}
|
| >
| Ian Lynagh writes:
| >
| > =============================================================
| > The (Interactive) Glasgow Haskell Compiler -- version 7.2.1
| > =============================================================
| >
| Ticket #3356 claims that {-# LANGUAGE NoTraditionalRecordSyntax #-} was
| implemented in 7.2.1.
|
| But GHCi v7.2.1 complains "Unsupported extension: NoTraditionalRecordSyntax".
|
| What (if anything) actually got implemented?
|
| Is/was the plan to be able to selectively 'prune' bits of record syntax? or
| just to completely banish anything with curly brackets {and their contents}
| from patterns, expressions and data declarations?
|
| I ask because I'd like to raise a ticket for
| http://hackage.haskell.org/trac/ghc/wiki/Records/DeclaredOverloadedRecordFie...
| ds
| /NoMonoRecordFields -- that is, to enable declaring within the same module
| multiple record types with the same field name.
|
| Of course it will also help when declaring the same field name in different
| (but imported) modules.
|
| Avoiding generating the (monomorphic) field selector function is a modest
| step towards freeing up the namespace, without in any way pre-judging how the
| 'narrow namespace issue' might get addressed.
|
| AntC
|
|
|
|
| _______________________________________________
| Glasgow-haskell-users mailing list
| Glasgow-haskell-users@haskell.org
| http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
