Feature suggestion: Invalid syntax red underlining

[avidrucker]

May we have added trigger error messages or warnings (aka the red squiggly underline) where instructions or data may have too many or not enough bits? At first, I thought perhaps syntax highlighting could be nice for this, such as making an entire line red if it is unrecognizable and/or possessing of too few or too many bits. After adding and removing bits from different lines, I think that the standard red underlining would be more effective and consistent with VS Code "bad syntax"/"syntax issues" behavior.

Bonus: Currently, lines are highlighted up to 16 bits, which seems appropriate. I believe it would be nice if a line was too many or too few bits that it not receive valid syntax highlighting to indicate that there is an issue (though I think this is a debatable opinion 😄), this would really put the cherry on the top IMO 😉

[lettucegoblin]

This would be amazing. I need to figure out how to separate the .bin/.a languages. it seems like it's done with scopes here

[avidrucker]

This could tie into us writing a linter perhaps 🤔 😁

[lettucegoblin]

Right now I have it checking to see if it's a .a/.bin file extension but if you dont have either and set the language to lcc you can write bin and ass right next to eachother LOL. Though having a non .a/.bin file isnt that common.

[avidrucker]

@lettucegoblin Shall we mark this as out of scope for now and close, or should we leave it open in case someone wants to take a stab at it?