summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTakenobu Tani <takenobu.hs@gmail.com>2020-08-06 18:51:14 +0900
committerBen Gamari <ben@smart-cactus.org>2020-08-06 19:46:46 -0400
commit9570c21295a2b4a1d1e40939869124f0b9b9bf91 (patch)
tree9d34401985571ab45cec45fdd59ca832ebd2f4aa
parent63348155404c64334fa864454132630f9d2a4d7f (diff)
downloadhaskell-9570c21295a2b4a1d1e40939869124f0b9b9bf91.tar.gz
users-guide: Rename 8.12 to 9.0
GHC 8.12.1 has been renamed to GHC 9.0.1. See also: https://mail.haskell.org/pipermail/ghc-devs/2020-July/019083.html [skip ci]
-rw-r--r--docs/users_guide/9.0.1-notes.rst (renamed from docs/users_guide/8.12.1-notes.rst)4
-rw-r--r--docs/users_guide/exts/lambda_case.rst2
-rw-r--r--docs/users_guide/exts/lexical_negation.rst2
-rw-r--r--docs/users_guide/exts/linear_types.rst2
-rw-r--r--docs/users_guide/exts/negative_literals.rst2
-rw-r--r--docs/users_guide/exts/qualified_do.rst2
-rw-r--r--docs/users_guide/release-notes.rst2
-rw-r--r--docs/users_guide/using-warnings.rst2
8 files changed, 9 insertions, 9 deletions
diff --git a/docs/users_guide/8.12.1-notes.rst b/docs/users_guide/9.0.1-notes.rst
index 28b9ceb541..45a796fb07 100644
--- a/docs/users_guide/8.12.1-notes.rst
+++ b/docs/users_guide/9.0.1-notes.rst
@@ -1,6 +1,6 @@
-.. _release-8-12-1:
+.. _release-9-0-1:
-Version 8.12.1
+Version 9.0.1
==============
The significant changes to the various parts of the compiler are listed in the
diff --git a/docs/users_guide/exts/lambda_case.rst b/docs/users_guide/exts/lambda_case.rst
index efcb6b6474..74bc84e164 100644
--- a/docs/users_guide/exts/lambda_case.rst
+++ b/docs/users_guide/exts/lambda_case.rst
@@ -25,7 +25,7 @@ Note that ``\case`` starts a layout, so you can write ::
...
pN -> eN
-Additionally, since GHC 8.12.1, combining :extension:`LambdaCase` with
+Additionally, since GHC 9.0.1, combining :extension:`LambdaCase` with
:extension:`Arrows` allows ``\case`` syntax to be used as a command in
``proc`` notation: ::
diff --git a/docs/users_guide/exts/lexical_negation.rst b/docs/users_guide/exts/lexical_negation.rst
index 1060d950e4..29f723dae1 100644
--- a/docs/users_guide/exts/lexical_negation.rst
+++ b/docs/users_guide/exts/lexical_negation.rst
@@ -7,7 +7,7 @@ Lexical negation
:shortdesc: Use whitespace to determine whether the minus sign stands for
negation or subtraction.
- :since: 8.12.1
+ :since: 9.0.1
Detect if the minus sign stands for negation during lexical analysis by
checking for the surrounding whitespace.
diff --git a/docs/users_guide/exts/linear_types.rst b/docs/users_guide/exts/linear_types.rst
index 1b725f36cc..48d102331f 100644
--- a/docs/users_guide/exts/linear_types.rst
+++ b/docs/users_guide/exts/linear_types.rst
@@ -4,7 +4,7 @@ Linear types
.. extension:: LinearTypes
:shortdesc: Enable linear types.
- :since: 8.12.1
+ :since: 9.0.1
Enable the linear arrow ``a #-> b`` and the multiplicity-polymorphic arrow
``a # m -> b``.
diff --git a/docs/users_guide/exts/negative_literals.rst b/docs/users_guide/exts/negative_literals.rst
index c2dbc1eff4..fb6cbc3c1f 100644
--- a/docs/users_guide/exts/negative_literals.rst
+++ b/docs/users_guide/exts/negative_literals.rst
@@ -24,7 +24,7 @@ will elicit an unexpected integer-literal-overflow message.
Whitespace can be inserted, as in ``- 123``, to force interpretation
as two tokens.
-In 8.12, the behavior of this extension changed, and now we require that a negative literal must not be preceded by a closing token (see
+In 9.0, the behavior of this extension changed, and now we require that a negative literal must not be preceded by a closing token (see
`GHC Proposal #229 <https://github.com/ghc-proposals/ghc-proposals/blob/master/proposals/0229-whitespace-bang-patterns.rst>`__
for the definition of a closing token). In other words, we parse ``f -123`` as ``f (-123)``, but ``x-123`` as ``(-) x
123``. Before this amendment, :extension:`NegativeLiterals` caused ``x-123`` to be parsed as ``x(-123)``.
diff --git a/docs/users_guide/exts/qualified_do.rst b/docs/users_guide/exts/qualified_do.rst
index 752628f379..90db9c8865 100644
--- a/docs/users_guide/exts/qualified_do.rst
+++ b/docs/users_guide/exts/qualified_do.rst
@@ -10,7 +10,7 @@ Qualified do-notation
.. extension:: QualifiedDo
:shortdesc: Enable qualified do-notation desugaring.
- :since: 8.12.1
+ :since: 9.0.1
Allow the use of qualified ``do`` notation.
diff --git a/docs/users_guide/release-notes.rst b/docs/users_guide/release-notes.rst
index 3fce057729..bb670e445a 100644
--- a/docs/users_guide/release-notes.rst
+++ b/docs/users_guide/release-notes.rst
@@ -4,4 +4,4 @@ Release notes
.. toctree::
:maxdepth: 1
- 8.12.1-notes
+ 9.0.1-notes
diff --git a/docs/users_guide/using-warnings.rst b/docs/users_guide/using-warnings.rst
index 2e96232e5a..afc3b18321 100644
--- a/docs/users_guide/using-warnings.rst
+++ b/docs/users_guide/using-warnings.rst
@@ -1767,7 +1767,7 @@ of ``-W(no-)*``.
:type: dynamic
:category:
- :since: 8.12
+ :since: 9.0
When the ``-haddock`` option is enabled, GHC collects documentation
comments and associates them with declarations, function arguments, data