Parsing issues are not detected for MISSING tokens #554

int main() {
     int var
}

└translation_unit
  └function_definition
    ├type: primitive_type int
    ├declarator: function_declarator
    │ ├declarator: identifier main
    │ └parameters: parameter_list
    │   ├(
    │   └)
    └body: compound_statement
      ├{
      ├declaration
      │ ├type: primitive_type int
      │ ├declarator: identifier foo
      │ └; 
      └}

When a source doesn't parse, tree-sitter emits two kinds of nodes: * "error" nodes, for things that aren't expected in that context * "missing" nodes, for nodes that are missing to make the context parse correctly We currently treat a source as syntactically incorrect when we encounter an `error` node, but not when we encounter `missing` ones. For instance: ```c int main() { int var } ``` is parsed by `mgf_dev parse` (in C) as: ``` └translation_unit └function_definition ├type: primitive_type int ├declarator: function_declarator │ ├declarator: identifier main │ └parameters: parameter_list │ ├( │ └) └body: compound_statement ├{ ├declaration │ ├type: primitive_type int │ ├declarator: identifier foo │ └; └} ``` Note the `;` token that actually missing from the source. It would likely be more consistent to reject those cases as well.