- The GHC runtime linker now uses ``LIBRARY_PATH`` and the runtime loader now also
searches ``LD_LIBRARY_PATH``.
-- The GHC runtime on Windows is no longer constrained by MAX_PATH.
+- The GHC runtime on Windows is no longer constrained by ``MAX_PATH``.
Template Haskell
~~~~~~~~~~~~~~~~
- ``($!)`` is now representation-polymorphic like ``($)``.
- The module ``Data.Functor.Contravariant`` has been moved from the
- ``contravariant`` package into base. All the other modules in
+ ``contravariant`` package into ``base``. All the other modules in
``contravariant`` (``Data.Functor.Contravariant.Divisible``, etc.)
have not been moved to ``base``, and they still reside in ``contravariant``.
~~~~~~~~~~~~~
Windows paths are not all the same. The different kinds of paths each have
-different meanings. The MAX_PATH limitation is not a limitation of the Operating
+different meanings. The ``MAX_PATH`` limitation is not a limitation of the Operating
System nor the File System. It is a limitation of the default namespace enforced
by the Win32 API for backwards compatibility.
The namespaces are:
- - file namespace: \\?\
- - device namespace: \\.\
- - nt namespace: \
+ - file namespace: ``\\?\``
+ - device namespace: ``\\.\``
+ - nt namespace: ``\``
Each of these turn off Path processing completely by the Win32 API and the paths
are passed untouched to the filesystem.
format to Win32 file namespace. By default the I/O manager will do two things to
your paths:
- - replace / with \\
+ - replace ``/`` with ``\\``
- expand relative paths to absolute paths
If you want to opt out of all preprocessing just expliticly use namespaces in