Commit d1594465 authored by Joachim Breitner's avatar Joachim Breitner
Browse files

Mention coerce in the release notes

It is not added to the section on Special built-in functions because
the (from a user POV related) unsafeCoerce has been removed there
parent 1534b1dc
......@@ -272,6 +272,27 @@
A new built-in function <literal>coerce</literal> is
provided that allows to safely coerce values between types
that have the same run-time-presentation, such as
newtypes, but also newtypes inside containers. See the
haddock documentation of
<ulink url="&libraryBaseLocation;/GHC-Exts.html#v%3Acoerce">coerce</ulink>
and of the class
<ulink url="&libraryBaseLocation;/GHC-Exts.html#t%3ACoercible">Coercible</ulink>
for more details.
This feature is included in this release as a technology
preview, and may change its syntax and/or semantics in the
next release.
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment