polserver/testsuite/escript/spread/syntax.src
Kevin Eady 3ccf701ce9
Format testsuite scripts, pol-core support modules (#713)
* Format escript testsuite

* Manual formatting for escript testsuite
- Add format-off to places where formatter does what it should, but we don't like the results
- Manually change places where formatter outputs weird things _without_ format-off, so next format-all would show changes if not fixed

* Update .err files; add update_err.py helper script

Use the format `:line:col: message` for all .err file checks. This
allows us to change the file names without needing to edit the .err
contents.

Note that `in/inc0{1,2}.err` need have error messages between POSIX and
Windows, so their messages are a bit more "generic" than the other errs.

* Format pol testsuite

* Manual formatting for pol testsuite

* Format pol-core modules

* Manual formatting for pol-core modules

* Additional format pol-core modules

Use FormatterLineWidth=10000 since module functions must be on one line
because of the parse_modules target

* Address Discord comments

- Support multi-line module function declarations in parse_modules

* Format on df07831
2024-10-04 10:29:55 +02:00

27 lines
601 B
Text

var foo := { 3 };
function bar( a, b, c, d, unused args ... )
endfunction
// bareArrayInitializer
{ 1, 2, foo ... };
{ 1, 2, foo ..., foo ..., { 1, 2, foo ..., foo ... } ... };
// functionCallSuffix
( @bar )( foo ... );
( @bar )( foo ..., 1, 2, foo ..., { 1, 2, 3 } ..., { { 1, 2, 3 } ..., 4 } );
// indexingSuffix -- NOT ALLOWED
// foo[1, 2, foo...];
// but the indexingSuffix can have children that are spread
foo[1, { 1, 2, foo ... }];
// methodCallSuffix
foo.bar( 1, 2, foo ... );
// functionCall
bar( a := 1, d := 2, c := 3, b := 4, foo ... );
// arrayInitializer
array{ 1, 2, foo ... };