Parse errors for mismatched brackets are awful

ghci> [foo
<interactive>:1:4: parse error (possibly incorrect indentation)

The parser error messages for incorrect brackets are awful. A much better message would be:

ghci> [foo
<interative>:1:1: bracket opened but not shut

i.e. refer to bracket issues, and say where the bracket started.

I realise this may be difficult within the current parser, but a simple post-processor for syntax errors could perhaps detect such errors. Also, while the { character and reasonably be about indentation, the others are much less likely to be.

Trac metadata

Trac field	Value
Version	6.6.1
Type	FeatureRequest
TypeOfFailure	OtherFailure
Priority	normal
Resolution	Unresolved
Component	Compiler
Test case
Differential revisions
BlockedBy
Related
Blocking
CC
Operating system	Unknown
Architecture	Unknown