* 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
The comparison (< and > operators) between objects of different types is
now based on object's addresses in memory. This leads to unpredictable results
and causes troubles with test scripts.
Proposed solution is:
- This is undefined behavior and could change in future, leave it undocumented
- Error and Undefined should always be < than any other object
- Objects of different type should compare < or > based on their Type ID
- Objects of the same type should always have comparison method implemented.
The code should not compile if those methods have not been implemented.
