Roger that. Thank you!

The message and the description need to be fixed, yes. Just leave this issue open and someone will take care of this.

I just checked the code of tests to make you able to m9ve forward before the problem gets addressed.

Yeah, well, that's the way it is. I had a variable called convertFunctions in my code and it was the variable that the anti-reader didn't like. Thank you @hobovsky for responding so quickly and helping me. However, I think it is either worth improving the error message. As I wrote above - You cannot do that doesn't say anything, given that there is no mention of Function being forbidden. Or could we update the description and add clearer requirements as to what is being tested in this test?

I will try to improve the message, but you'd have to tell me the language you are attempting.

EDIT: your solution most probably triggers this condition of the anti-cheat: sol.includes('Function').

I'm trying to post my solution and I keep getting an error from anti-chit - You cannot do that. What exactly can't I do, what do I need to fix? I'm tired of playing the guessing game. These rules should be clearly spelled out. I realize it probably doesn't like some of the naming in my code, but I shouldn't have to guess, the error should clearly tell me what needs to be changed. JSON.parse and eval I understandably don't use.

Prolog translation

Agree

Description doesn't mention spaces at all ATM. That would be good to update as well then.

Except that spec is not part of the description, we are already using simplifications here and there, and the JS tests are not unordered either ( they could have been, with assertDeepEquals, but they are not, with assertSimilar ). Because JS does have something of an ordering in objects, at least sometimes ( and sometimes not ).

It's a bit of a wasps' nest. But I tend towards wanting to preserve existing ordering, and the source has an ordering.

( I may not have thought of all this when translating or when having visions of nightmares. )

Note that I don't get notifications for this thread. If the translation must be updated, please comment on the translation suggestion.

js at least: missing a fixed test with a string beginning with a whitespace. Fortunately, it appears frequently in the random tests, but having it in the fixed tests would be more comfortable. Increasing a bit the number of random tests would be a good idea too, to be sure tha nobody can slip through the tests.

That's a nightmare to test, at least in Haskell.

Only because it uses the wrong type.
https://tools.ietf.org/html/rfc8259

An object is an unordered collection...

It should be a Map in the first place.

Please not. That's a nightmare to test, at least in Haskell.

Fixed. I think.

Is it OK now?

True and False are mentioned as result values, not input values. true and false ( and null ) are specified under value. These are intended as literal strings.

This is consistent with normal JSON.