Zubin pushed to branch ghc-10.0 at Glasgow Haskell Compiler / GHC Commits: 53fd9e34 by Vladislav Zavialov at 2026-04-27T22:00:02+03:00 Replace GHC 9.16 references with GHC 10.0 - - - - - 10 changed files: - compiler/GHC/Driver/Flags.hs - docs/users_guide/debug-info.rst - docs/users_guide/exts/explicit_namespaces.rst - docs/users_guide/exts/linear_types.rst - docs/users_guide/exts/modifiers.rst - docs/users_guide/exts/qualified_strings.rst - docs/users_guide/exts/required_type_arguments.rst - docs/users_guide/using-warnings.rst - docs/users_guide/using.rst - testsuite/tests/typecheck/should_fail/all.T Changes: ===================================== compiler/GHC/Driver/Flags.hs ===================================== @@ -1112,9 +1112,9 @@ data WarningFlag = -- ^ @since 9.14, scheduled to be removed in 9.18 -- -- See Note [Quantifying over equalities in RULES] in GHC.Tc.Gen.Sig - | Opt_WarnUnusableUnpackPragmas -- Since 9.14 - | Opt_WarnPatternNamespaceSpecifier -- Since 9.14 - | Opt_WarnUnrecognisedModifiers -- ^ @since 9.16 + | Opt_WarnUnusableUnpackPragmas -- ^ @since 9.14 + | Opt_WarnPatternNamespaceSpecifier -- ^ @since 9.14 + | Opt_WarnUnrecognisedModifiers -- ^ @since 10.0 deriving (Eq, Ord, Show, Enum, Bounded) -- | Return the names of a WarningFlag @@ -1377,7 +1377,7 @@ standardWarnings -- see Note [Documenting warning flags] Opt_WarnTypeEqualityRequiresOperators, Opt_WarnInconsistentFlags, Opt_WarnTypeEqualityOutOfScope, - Opt_WarnImplicitRhsQuantification, -- was in -Wcompat since 9.8, enabled by default since 9.14, to turn into a hard error in 9.16 + Opt_WarnImplicitRhsQuantification, -- was in -Wcompat since 9.8, enabled by default since 9.14, to turn into a hard error in 10.2 (#25911) Opt_WarnViewPatternSignatures, Opt_WarnUselessSpecialisations, Opt_WarnDeprecatedPragmas, ===================================== docs/users_guide/debug-info.rst ===================================== @@ -478,7 +478,7 @@ to a source location. This lookup table is generated by using the ``-finfo-table :type: dynamic :category: debugging - :since: 9.16 + :since: 10.0 Disable generation of distinct info tables for all constructors. @@ -488,7 +488,7 @@ to a source location. This lookup table is generated by using the ``-finfo-table :type: dynamic :category: debugging - :since: 9.16 + :since: 10.0 The entries in the info table map resulting from :ghc-flag:`-fdistinct-constructor-tables` flag may significantly ===================================== docs/users_guide/exts/explicit_namespaces.rst ===================================== @@ -121,7 +121,7 @@ there is a need to support older GHC versions. Wildcards in import/export lists ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -**Since:** GHC 9.16 +**Since:** GHC 10.0 Namespace-specified wildcards ``type ..`` and ``data ..`` may be used to import all names in the corresponding namespace from a module: :: ===================================== docs/users_guide/exts/linear_types.rst ===================================== @@ -318,7 +318,7 @@ hidden; it is an essential part of the exposed interface.) Interaction with Modifiers -------------------------- -Since GHC version 9.16, Linear types use :extension:`Modifiers` syntax, and by +Since GHC version 10.0, Linear types use :extension:`Modifiers` syntax, and by default enable that extension. In earlier versions, linear types used a more restricted variant of that syntax. ===================================== docs/users_guide/exts/modifiers.rst ===================================== @@ -6,7 +6,7 @@ Modifiers .. extension:: Modifiers :shortdesc: Allow experimental modifier syntax. - :since: 9.16 + :since: 10.0 :status: Experimental Enable modifier syntax in various places, such as arrows (``a %m -> b``) and @@ -138,10 +138,10 @@ and limitations. let %1 (Just x) = ... -- (2b) let %1 !(Just x) = ... -- (2c) - In 9.14, (1a) and (2a) parsed as (1b) and (2b) respectively. From 9.16, (1a) + In 9.14, (1a) and (2a) parsed as (1b) and (2b) respectively. From 10.0, (1a) parses as (1d), and (2a) fails to parse. - Note that linear bindings must be strict. (1c) and (2c) parse in 9.16 the same + Note that linear bindings must be strict. (1c) and (2c) parse in 10.0 the same as in 9.14. But with ``-XStrict`` enabled, (1a) and (2a) would previously have been accepted, and are now rejected, even with ``-XLinearTypes -XNoModifiers``. ===================================== docs/users_guide/exts/qualified_strings.rst ===================================== @@ -6,7 +6,7 @@ Qualified string literals .. extension:: QualifiedStrings :shortdesc: Enable qualified string literals. - :since: 9.16.1 + :since: 10.0.1 Enable qualified string literals. ===================================== docs/users_guide/exts/required_type_arguments.rst ===================================== @@ -303,7 +303,7 @@ A few limitations apply: * In term syntax, in positions where ``*`` is a direct argument to ``->``, e.g. in ``f (* -> * -> *)`` and ``f (* -> Constraint)``, the ``*``\s stand for ``Type``, provided the :extension:`StarIsType` extension is enabled. - This is supported from GHC 9.16 onwards; earlier versions will produce + This is supported from GHC 10.0 onwards; earlier versions will produce a parse error. What to do instead: use ``Type`` from the ``Data.Kind`` module. ===================================== docs/users_guide/using-warnings.rst ===================================== @@ -2711,7 +2711,7 @@ of ``-W(no-)*``. :type: dynamic :reverse: -Wno-unrecognised-modifiers - :since: 9.16 + :since: 10.0 :default: on ===================================== docs/users_guide/using.rst ===================================== @@ -1618,7 +1618,7 @@ Some flags only make sense for particular target platforms. :type: dynamic :category: platform-options - :since: 9.16.1 + :since: 10.0.1 :implies: :ghc-flag:`-mavx512f` (x86 only) This flag allows the code generator (whether the :ref:`native code generator <native-code-gen>` @@ -1639,7 +1639,7 @@ Some flags only make sense for particular target platforms. :type: dynamic :category: platform-options - :since: 9.16.1 + :since: 10.0.1 :implies: :ghc-flag:`-mavx512f` (x86 only) This flag allows the code generator (whether the :ref:`native code generator <native-code-gen>` @@ -1684,7 +1684,7 @@ Some flags only make sense for particular target platforms. :type: dynamic :category: platform-options - :since: 9.16.1 + :since: 10.0.1 :implies: :ghc-flag:`-mavx512f` (x86 only) This flag allows the code generator (whether the :ref:`native code generator <native-code-gen>` @@ -1823,7 +1823,7 @@ Some flags only make sense for particular target platforms. :type: dynamic :category: platform-options - :since: 9.16.1 + :since: 10.0.1 (x86 only) This flag allows the code generator (whether the :ref:`native code generator <native-code-gen>` or the :ref:`LLVM backend <llvm-code-gen>`) to emit x86 GFNI instructions. ===================================== testsuite/tests/typecheck/should_fail/all.T ===================================== @@ -720,7 +720,7 @@ test('T17940', normal, compile_fail, ['']) test('ErrorIndexLinks', normal, compile_fail, ['-fprint-error-index-links=always']) test('T24064', normal, compile_fail, ['']) test('T24090a', normal, compile_fail, ['']) -test('T24090b', normal, compile, ['']) # scheduled to become an actual error in GHC 9.16 +test('T24090b', normal, compile, ['']) # scheduled to become an actual error in GHC 10.2 (#25911) test('T24298', normal, compile_fail, ['']) test('T24279', normal, compile, ['']) # Now accepted (Nov 2025) test('T24318', normal, compile_fail, ['']) View it on GitLab: https://gitlab.haskell.org/ghc/ghc/-/commit/53fd9e344713c2d826ba62a9c07d6c48... -- View it on GitLab: https://gitlab.haskell.org/ghc/ghc/-/commit/53fd9e344713c2d826ba62a9c07d6c48... You're receiving this email because of your account on gitlab.haskell.org.