I added asserts in the test cases (and in the solution for some checks at another level). Please tell me if there remain some issues.

Ok, I will study that. Thanks for the feedback!

If somebody sends me a link to this kata, does it count as being rickrolled?

It's just to know whether I should punch them or not.

Apparently cubic time passes the test. Ashamed to have had to submit though.

Thank you too. :-)

I wanted to check whether this kata existed, and now I have confirmation I fear the moment when I try it. :-)

For the test in Caml, we get a warning because of the use of the now deprecated functions (lower|upper)case. It would be nice to edit the kata and replace by the same function with _ascii appended to the name.

Hi,

Actually, the rules forbid the use of nonpositive integers, as well as non integers.
Your solution may as well be [[2, '-', 1], [6, '+', 25], [100, '-', 1], [31, '+', 99], [7, '*', 130]], which would be accepted.

I am confident that the implementation of this rule is easy and will validate your code. :)

Thank you for the quick reply!

I actually used the Big_int module, but there is no big difference.

Unfortunately, the servers seem unavailable for the tests, so I cannot try again currently.

Edit: servers are working again, and everyhing is now fine.

Problem while submitting in OCaml (testing works):

File "(stdin)", line 16, characters 22-25:
Error: Unbound constructor Int

In the end, I was so puzzled by the error for n = 2, until I noticed that Python2 was used. XS

(A0 = Informatique. Au cas où d'autres Cachanais se retrouveraient ici.)

Oh, I swiched between the parts, so? My bad. Well, I used another way, meanwhile.
Thank you again. :)

Thank you for reporting the problem.

As it is my first kata, I wondered how to implement random tests with the correct solution and hoped that example tests concealed the code.

I am going to look how to fix it.