Added this to the Later milestone.

The error is that you can't have both final and const. The most correct highlighting would be to highlight both and say that they are mutually exclusive.

This comment was originally written by @mhausner

Sure. But in order to give more accurate error messages, you have to make an educated guess as to what the illegal declaration was intended to be. Looking at this example as a human, it's obvious, but to a parser it is not obvious. You can add heuristics and they may work for some cases, but not in other cases and you are back to square one. I'm tempted to just make this particular error say "syntax error".

Apart from the error message which can be more or less helpful, the main issue was the position of the error which should be trivial to fix: The error clearly occurs after 'const' when encountering the unexpected 'final', and not before 'const'.

This comment was originally written by @mhausner

The explanation for the error location follows from what I said earlier: the compiler doesn't know what to do with the entire line, so it reports the error on the first token of the declaration. I don't want to put more hacks/heuristics into the compiler that just solve this one case. At least not at this point.

Removed this from the Later milestone.
Added Oldschool-Milestone-Later label.

Removed Oldschool-Milestone-Later label.

This comment was originally written by @mhausner

As I outlined in previous comments, there is no bug here. I don't want to add more heuristics into the parser that guess what an illegal sequence of tokens could have been meant to be.

Added AsDesigned label.