summaryrefslogtreecommitdiff
path: root/testsuite/tests/parser/should_fail/readFail034.stderr
diff options
context:
space:
mode:
authorBen Gamari <bgamari.foss@gmail.com>2015-06-16 20:01:22 +0200
committerBen Gamari <ben@smart-cactus.org>2015-06-16 20:01:22 +0200
commit1ff7f09b3abedb2a6daf384b55ad3d0134f0d174 (patch)
tree34ad913bdc6f19ab1151d90cfa14e4aedf9ffe58 /testsuite/tests/parser/should_fail/readFail034.stderr
parentb0d8ba368f031279444c851dbca499d7e272f74c (diff)
downloadhaskell-1ff7f09b3abedb2a6daf384b55ad3d0134f0d174.tar.gz
Lexer: Suggest adding 'let' on unexpected '=' token
Summary: I've heard numerous fledgling Haskeller's complain about the behavior of ghci regarding bindings. While most REPLs accept bindings of the form `x = 42`, GHCi is implicitly a `do` block, meaning that the user must know to use a `let` to introduce a binding. Here we suggest to the user that they may need a `let` and give them a small example in the event that we find an unexpected `=` token. Reviewers: austin Reviewed By: austin Subscribers: thomie, bgamari Differential Revision: https://phabricator.haskell.org/D980
Diffstat (limited to 'testsuite/tests/parser/should_fail/readFail034.stderr')
-rw-r--r--testsuite/tests/parser/should_fail/readFail034.stderr5
1 files changed, 4 insertions, 1 deletions
diff --git a/testsuite/tests/parser/should_fail/readFail034.stderr b/testsuite/tests/parser/should_fail/readFail034.stderr
index 027d0ca13f..75156c9ae4 100644
--- a/testsuite/tests/parser/should_fail/readFail034.stderr
+++ b/testsuite/tests/parser/should_fail/readFail034.stderr
@@ -1,2 +1,5 @@
-readFail034.hs:4:6: parse error on input ‘=’
+readFail034.hs:4:6: error:
+ parse error on input ‘=’
+ Perhaps you need a 'let' in a 'do' block?
+ e.g. 'let x = 5' instead of 'x = 5'