such as in the equation
 o1,o2 = current (n(x,y,z));

(It would have avoided issue #8)

close #8

Remove a lot of warnings (considered as errors by dune).

cd rdbg #sha 4a54c7a1181e1200670f3eaf14af1be32823cd04

Indeed the API of Format.formatter_out_functions changed in 4.06.0

To turn around this problem, I've used pp_get_formatter_out_functions
and extend it result

Rationale: a step to make time traveling work correctly.

https://www.npmjs.com/package/semantic-release-gitlab

from https://semver.org/ :
  Given a version number MAJOR.MINOR.PATCH, increment the:

  - MAJOR version when you make incompatible API changes,
  - MINOR version when you add functionality in a backwards-compatible manner, and
  - PATCH version when you make backwards-compatible bug fixes.

For MAJOR, choosing 6 is obvious.

From Minor it's not clear. This number is supposed to reflect the number of
add functuionnality, so starting at 0 is not great.

The current version is 1.762, but starting at 762 would be wrong too,
as most do not deals with new functionnalyties.

In a ideal word, I should use the log and tag every commit tha deals with a new
functionnalyty, but there is a lot of commits (762).

Hence I,'ve decided to choose 100.

It causes bad error messages in the case were the parametric node is undefined.

e.g., the equation

  S=if(M[n-1]) then (entiernat<<n>>(M)-puiss<<n+1>>(2)) else entiernat<<n>>(M);

raises "Error: Bad number of (static) arguments: 0 expected, and 1 provided."
when entiernat is undefined

It seems useless because no test is broken. The comment mention node
parameters that themselves have parameters. But it is the case for
test/should_work/Gyroscope2.lus, and it is still working.