some casts have to be reinterpret_casts because of type incompatibility
between unsigned char * and char *

ints unnecessarily reduce range of values for indexes

remove not needed cast

Map keys are exactly corresponding to vector indexes in the algorithm.

getRank used to return a class that was supposed to be compatible with
unsigned (and size_t) however now it is unsigned by itself

the field has its default value specified, no need for the initializer

int to char is expected so cast; double to in was incorrect should
return double

The common abreviation for microseconds is us.

In recent Arch Linux builds we encountered some timeouts in tests.
Interestingly, the 30s timeouts were encountered not after 30s but
right-away. See the ctest output attached at the end of the message.

I remembered that Arch switched to glibc=2.33 recently. And by stracing
the test process I have noticed that indeed, the select in waitSignalTimeout
function timeouted early.
It seemed that the timeval struct is the problem and indeed it was. It
didn't like setting the 30s timeout as {.tv_sec = 0, .tv_usec = 30 *
1000 * 1000}. However, I can't find in any manpage why this is wrong...

It seems to be fixed by limiting tv_usec to be from [0; 1000*1000)
range and transfer the whole seconds into the tv_sec field.
And the glibc docs [1] says it so explicitely:

> When struct timeval values are produced by GNU C Library functions,
> the value in this field will always be greater than or equal to zero,
> and less than 1,000,000. When struct timeval values are supplied to GNU
> C Library functions, the value in this field must be in the same range.

[1] https://www.gnu.org/software/libc/manual/html_mono/libc.html#Time-Types

 -------------------------------------------------------------------------------
 aql/AutomatonIteration.aql
 -------------------------------------------------------------------------------
 /builds/algorithms-library-toolkit/infrastructure/cd-release/src/algorithms-library-snapshot/build/tests/AutomatonIteration.cpp:17
 ...............................................................................

 /builds/algorithms-library-toolkit/infrastructure/cd-release/src/algorithms-library-snapshot/tests/testing/TimeoutAqlTest.cpp:206: warning:
   AqlTest: timeout (30000000 us) reached
   Trying to execute testfile /builds/algorithms-library-toolkit/infrastructure/cd-release/src/algorithms-library-snapshot/tests/aql/AutomatonIteration.aql

 Seed was: 1053288110
   Child aqlout was: ><
   Child stdout was: ><
   Child stderr was: ><

 /builds/algorithms-library-toolkit/infrastructure/cd-release/src/algorithms-library-snapshot/tests/testing/TimeoutAqlTest.cpp:208: FAILED:

 ===============================================================================
 test cases: 1 | 1 failed
 assertions: 3 | 2 passed | 1 failed

Start working on custom code-style/code-requirements file checker.
So far we check only for missing license, for non-standard EOL (\r) and
for files that not-compliant with clang-format.

... because most developers were copy-pasting the preambule anyway and
did not pay any attention to change it.

Also, I think that git does better job in managing that.

The parents were set incorrectly in swap of trees and tries. Parents in children
of swapped objects should be set, not the parents in swapped objects.

The template function sort internally called swap so it internaly tests
swap of trees

Take out common code in then and else branch

The case (b*+a)* was only optimized to (b+a)* by lemma V4.

This test generates a random automaton, runs both iteration algorithms on
it and then tests that both these automata accept equal language.

This is first of the aql integration tests (which support was added in
commit d79fe028). This should serve as
an example how to write aql integration tests.
Also, this is something that should not be in the unit tests (and it
was removed in the previous commits).