On 05/01/19 18:51, Ryan Joseph wrote: > Given the new syntax requirements we talked about there needs to be a ; after T now. What error should be used if there isn’t a ; semicolon separator between types and consts? I just used a parser_e_illegal_expression for now. scan_f_syn_expected=02003_F_Syntax error, "$1" expected but "$2" found Jonas