tests/invalid/*.{m,err_exp}:
tests/misc_tests/*.m:
tests/mmc_make/*.m:
tests/par_conj/*.m:
tests/purity/*.m:
tests/stm/*.m:
tests/string_format/*.m:
tests/structure_reuse/*.m:
tests/submodules/*.m:
tests/tabling/*.m:
tests/term/*.m:
tests/trailing/*.m:
tests/typeclasses/*.m:
tests/valid/*.m:
tests/warnings/*.{m,exp}:
Make these tests use four-space indentation, and ensure that
each module is imported on its own line. (I intend to use the latter
to figure out which subdirectories' tests can be executed in parallel.)
These changes usually move code to different lines. For the tests
that check compiler error messages, expect the new line numbers.
browser/cterm.m:
browser/tree234_cc.m:
Import only one module per line.
tests/hard_coded/boyer.m:
Fix something I missed.
for variables in lambda goals.
compiler/quantification.m:
(1) When implicitly-quantifying a lambda goal, the "lambda-outsidevars"
should be set to the empty set, so that variables occurring
only inside disjoint lambda goals are locally quantified
inside those lambda goals.
(2) When quantifying conjunctions and if-then-elses, use both
the lambda outsidevars and the ordinary outsidevars when
computing the non-locals, rather than just using the
ordinary outsidevars.
tests/valid/lambda_quant.m:
Add another test case for bug (1).
There was already a tests in this module that was supposed to
test this sort of stuff, but that test case happened to work,
because the effects of bugs (1) and (2) cancelled out. :-(
tests/valid/Mmake:
tests/valid/lambda_quant_bug.m:
Add a regression test for bug (2).
Estimated hours taken: 0.25
tests/valid:
Add a test case to test quantification of lambda
expressions, and using variables as goals (rather than
using call/1 explicitly).
