If I have a goto where the destination is just a plain uninterpolated string, and there's no label matching that string, then I've probably left something unfinished or made a typo. The computer can be better than I am at looking at all the labels to see whether there's a matching one, and it could let me know about it (in a softer way than failing validation). Highlighting the label string in a different color seems like a good way for it to do that. (Of course, if there's any string interpolation involved, that's different; I imagine this highlight only happening to strings without interpolation.)
Similar logic applies in other cases, such as:
- Teleporting to a nonexistent board name
- Sending to a nonexistent robot name
- Playing a MOD or SAM file that doesn't exist
- Malformed expression
- Out-of-range color or parameter value
and probably others.
Since robot names can change at runtime, and files can be written at runtime, a string that statically doesn't match those isn't necessarily actually wrong, but it's an unusual enough case that a non-binding "hey, this string is unusual" highlight from the editor still seems like a net positive.
Help
