Skip to content

GitLab

Commit ead1eed0 authored by simonpj@microsoft.com's avatar simonpj@microsoft.com
Browse files
Options

Fix flag name -XDisambiguateRecordFields

parent 1d14a6cd
Hide whitespace changes
Inline Side-by-side
Showing with 3 additions and 3 deletions
docs/users_guide/flags.xml
View file @ ead1eed0
......@@ -659,11 +659,11 @@
<entry><option>-XNoArrows</option></entry>
</row>
<row>
<entry><option>-fdisambiguate-record-fields</option></entry>
<entry><option>-XDisambiguateRecordFields</option></entry>
<entry>Enable <link linkend="disambiguate-fields">record
field disambiguation</link></entry>
<entry>dynamic</entry>
<entry><option>-fno-disambiguate-record-fields</option></entry>
<entry><option>-XNoDisambiguateRecordFields</option></entry>
</row>
<row>
<entry><option>-XForeignFunctionInterface</option></entry>
......
docs/users_guide/glasgow_exts.xml
View file @ ead1eed0
......@@ -1232,7 +1232,7 @@ it is not clear which of the two types is intended.
</para>
<para>
Haskell 98 regards all four as ambiguous, but with the
<option>-fdisambiguate-record-fields</option> flag, GHC will accept
<option>-XDisambiguateRecordFields</option> flag, GHC will accept
the former two. The rules are precisely the same as those for instance
declarations in Haskell 98, where the method names on the left-hand side
of the method bindings in an instance declaration refer unambiguously
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment