nix/tests/functional/lang/eval-fail-bad-string-interpolation-1.err.exp

error:
       … while evaluating a path segment
         at /pwd/lang/eval-fail-bad-string-interpolation-1.nix:1:2:
            1| "${x: x}"
             |  ^
            2|

       error: cannot coerce a function to a string: «lambda @ /pwd/lang/eval-fail-bad-string-interpolation-1.nix:1:4»
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 20:23:08 +00:00			`error:`
			`… while evaluating a path segment`
			`at /pwd/lang/eval-fail-bad-string-interpolation-1.nix:1:2:`
			`1\| "${x: x}"`
			`\| ^`
			`2\|`

Print the value in `error: cannot coerce` messages This extends the `error: cannot coerce a TYPE to a string` message to print the value that could not be coerced. This helps with debugging by making it easier to track down where the value is being produced from, especially in errors with deep or unhelpful stack traces. 2023-12-06 20:42:53 +00:00			`error: cannot coerce a function to a string: «lambda @ /pwd/lang/eval-fail-bad-string-interpolation-1.nix:1:4»`