nix-super/tests/functional/lang/parse-fail-undef-var-2.err.exp

error: syntax error, unexpected ':', expecting '}' or ','
       at «stdin»:3:13:
            2|
            3|   f = {x, y : ["baz" "bar" z "bat"]}: x + y;
             |             ^
            4|
parser.y: eliminate conflicts 2024-07-20 19:04:25 +03:00			`error: syntax error, unexpected ':', expecting '}' or ','`
Expanded test suite * Lang now verifies errors and parse output * Some new miscellaneous tests * Easy way to update the tests * Document workflow in manual * Use `!` not `~` as separater char for sed It is confusing to use `~` when we are talking about paths and home directories! * Test test suite itself (`test/lang-test/infra.sh`) Additionally, run shellcheck on `tests/lang.sh` to help ensure it is correct, now that is is more complex. Co-authored-by: Robert Hensing <roberth@users.noreply.github.com> Co-authored-by: Valentin Gagarin <valentin.gagarin@tweag.io> 2015-09-04 23:23:08 +03:00			`at «stdin»:3:13:`
			`2\|`
keep copies of parser inputs that are in-memory only the parser modifies its inputs, which means that sharing them between the error context reporting system and the parser itself can confuse the reporting system. usually this led to early truncation of error context reports which, while not dangerous, can be quite confusing. 2024-01-29 07:19:23 +02:00			`3\| f = {x, y : ["baz" "bar" z "bat"]}: x + y;`
Expanded test suite * Lang now verifies errors and parse output * Some new miscellaneous tests * Easy way to update the tests * Document workflow in manual * Use `!` not `~` as separater char for sed It is confusing to use `~` when we are talking about paths and home directories! * Test test suite itself (`test/lang-test/infra.sh`) Additionally, run shellcheck on `tests/lang.sh` to help ensure it is correct, now that is is more complex. Co-authored-by: Robert Hensing <roberth@users.noreply.github.com> Co-authored-by: Valentin Gagarin <valentin.gagarin@tweag.io> 2015-09-04 23:23:08 +03:00			`\| ^`
keep copies of parser inputs that are in-memory only the parser modifies its inputs, which means that sharing them between the error context reporting system and the parser itself can confuse the reporting system. usually this led to early truncation of error context reports which, while not dangerous, can be quite confusing. 2024-01-29 07:19:23 +02:00			`4\|`