Skip to content
Snippets Groups Projects
Commit d4c43df1 authored by Zubin's avatar Zubin Committed by Marge Bot
Browse files

Update docs for change in parsing behaviour of infix operators like in GHC 9

parent 46c2d0b0
No related branches found
No related tags found
No related merge requests found
......@@ -246,9 +246,15 @@ Language
as ``f (-123)``, but ``x-123`` as ``(-) x 123``. Before this amendment,
:extension:`NegativeLiterals` caused ``x-123`` to be parsed as ``x(-123)``.
* GHC now requires whitespace between infix operators and their arguments in
some cases where it was not previously necessary as the result of the
* GHC is now more sensitive to whitespace between infix operators and their arguments,
requiring it in some cases where it was not previously necessary as the result of the
:ref:`whitespace-sensitive operator parsing proposal <https://github.com/ghc-proposals/ghc-proposals/pull/229>`.
It also affects the usage of ``!``,``~`` and ``@`` as BangPatterns, irrefutable patterns
and type applications respectively.
This means that expressions that were parsed as visible type applications
in previous versions when the ``@`` was surrounded by whitespace will now
be parsed as an operator application.
For more details see the `migration guide on the wiki <https://gitlab.haskell.org/ghc/ghc/-/wikis/migration/9.0#whitespace-sensitive-and->`.
Compiler
~~~~~~~~
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment