On Wed, 04 Oct 2017 22:10:22 -0700, [email protected] wrote:
> To produce an error message that is more precise we'll need more
> information
> than just a line number, but we don't have that during the run time.
Couldn't the confusing wording be fixed without additional information?
As I understand it, the problem with the current message is that the
in '⏏~' (indicated by ⏏)
part leads people to think it's referring to a position in the source code,
when it is actually referring to a position in a string. Especially because the
"in block ... in file ... at line ..." line comes directly after it.
