From 9a3e1657db4c0292fc06d6183a802af631c3666a Mon Sep 17 00:00:00 2001 From: David Kraeutmann Date: Tue, 7 Jul 2015 16:59:52 +0200 Subject: Deferred type errors now throw TypeError (#10284) Depends on D864. Previous behaviour was ErrorCall, which might mask issues in tests using -fdefer-type-errors Signed-off-by: David Kraeutmann Test Plan: Test whether the error thrown is indeed TypeError and not ErrorCall. Reviewers: hvr, nomeata, austin Reviewed By: nomeata, austin Subscribers: nomeata, simonpj, thomie Differential Revision: https://phabricator.haskell.org/D866 GHC Trac Issues: #10284 --- docs/users_guide/glasgow_exts.xml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) (limited to 'docs') diff --git a/docs/users_guide/glasgow_exts.xml b/docs/users_guide/glasgow_exts.xml index 95f814f0d0..6d69c75faf 100644 --- a/docs/users_guide/glasgow_exts.xml +++ b/docs/users_guide/glasgow_exts.xml @@ -9196,11 +9196,11 @@ main = print "b" At runtime, whenever a term containing a type error would need to be - evaluated, the error is converted into a runtime exception. - Note that type errors are deferred as much as possible during runtime, but - invalid coercions are never performed, even when they would ultimately - result in a value of the correct type. For example, given the following - code: + evaluated, the error is converted into a runtime exception of type + TypeError. Note that type errors are deferred as much + as possible during runtime, but invalid coercions are never performed, + even when they would ultimately result in a value of the correct type. + For example, given the following code: x :: Int x = 0 @@ -9211,7 +9211,7 @@ y = x z :: Int z = y - evaluating z will result in a runtime type error. + evaluating z will result in a runtime TypeError. Deferred type errors in GHCi -- cgit v1.2.1