Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
GHC
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
CSEdd
GHC
Commits
d4c43df1
Commit
d4c43df1
authored
3 years ago
by
Zubin
Committed by
Marge Bot
3 years ago
Browse files
Options
Downloads
Patches
Plain Diff
Update docs for change in parsing behaviour of infix operators like in GHC 9
parent
46c2d0b0
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/users_guide/9.0.1-notes.rst
+8
-2
8 additions, 2 deletions
docs/users_guide/9.0.1-notes.rst
with
8 additions
and
2 deletions
docs/users_guide/9.0.1-notes.rst
+
8
−
2
View file @
d4c43df1
...
...
@@ -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
~~~~~~~~
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment