This is a small nit, but the lex error when forgetting to access a qualified identifier seems a bit misleading. I think we could probably make this particular error more specific for the actual cause, which (imo) is likely that the user forgot to finish what they were typing. (For example, today I was looking around my file for strange whitespace characters without realizing I had just forgotten to finish what I was typing!)
For example, in the following code:
You get the lex error
Illegal whitespace character U+0020
@natefaubion suggested we could have an error that says Whitespace not allowed in qualified identifier or similar.
You get a similar error for when you forget to access an unqualified identifier, such as
resulting in
Unexpected or mismatched indentation
(I'm not sure if the second one is as easy to clean up, but I think the first example is relatively straightforward)
Has anyone else had a similar experience, or have a suggestion for a more specific error message?
This is a small nit, but the lex error when forgetting to access a qualified identifier seems a bit misleading. I think we could probably make this particular error more specific for the actual cause, which (imo) is likely that the user forgot to finish what they were typing. (For example, today I was looking around my file for strange whitespace characters without realizing I had just forgotten to finish what I was typing!)
For example, in the following code:
You get the lex error
Illegal whitespace character U+0020
@natefaubion suggested we could have an error that says Whitespace not allowed in qualified identifier or similar.
You get a similar error for when you forget to access an unqualified identifier, such as
resulting in
Unexpected or mismatched indentation
(I'm not sure if the second one is as easy to clean up, but I think the first example is relatively straightforward)
Has anyone else had a similar experience, or have a suggestion for a more specific error message?