mirror of
https://github.com/Mercury-Language/mercury.git
synced 2026-04-18 19:03:45 +00:00
fdd141bf77
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.
51 lines
1.5 KiB
Mathematica
51 lines
1.5 KiB
Mathematica
%---------------------------------------------------------------------------%
|
|
% vim: ts=4 sw=4 et ft=mercury
|
|
%---------------------------------------------------------------------------%
|
|
|
|
:- module mode_selection.
|
|
:- interface.
|
|
:- import_module io.
|
|
|
|
:- pred main(io::di, io::uo) is det.
|
|
|
|
:- implementation.
|
|
:- import_module require.
|
|
|
|
% Currently (May 2001) we don't pass this test case,
|
|
% because the compiler's expression flattening puts
|
|
% the sub-goals in top-down order, rather than
|
|
% (as the language reference manual requires)
|
|
% ordering them bottom-up. This means that the call to
|
|
% func2 gets flattened as
|
|
% { V_1 = func2(In, V_2) },
|
|
% { V_2 = In },
|
|
% { print(V_1) }
|
|
% rather than as
|
|
% { V_1 = func2(In, V_2) },
|
|
% { V_2 = In },
|
|
% { print(V_1) }
|
|
% which causes mode analysis to select the wrong mode in the
|
|
% call to func2, which in turn causes a determinism error.
|
|
%
|
|
% The rationale for keeping the current behaviour is that
|
|
% the naive fix of just flattening to bottom-up order
|
|
% causes performance problems in type checking, in particular
|
|
% when compiling compiler/options.m.
|
|
% Eventually we ought to change the type checker to use
|
|
% a different algorithm that doesn't have this performance
|
|
% problem, then we can fix flattening, and this test case
|
|
% will then pass.
|
|
|
|
main -->
|
|
{ In = 42 },
|
|
print(func2(In, In)), nl.
|
|
|
|
:- func func2(int, int) = string.
|
|
:- mode func2(in, in) = out is det.
|
|
:- mode func2(in, out) = out is det.
|
|
:- mode func2(out, in) = out is det.
|
|
:- mode func2(out, out) = out is det.
|
|
|
|
func2(_, _) = _ :-
|
|
error("called func2/2").
|