I personally don't think that's enough to approve this kata.

Waiting for the opinion of other users.

Hard to say, most requirements have been done in other kata's. However, the sum function, and possibly multi-leveled nested expressions with this function, is a unique requirement. Ideally, we would have just one expressions kata (in the purple region) that covers all the requirements from existing kata's.

Debatable, but to prevent prematurated approval:

Isn't the kata just another dup of the many calculators kata? (I'm specifically thinking about the C# one, which uses some similar concepts)

Is this kata approvable for your taste B4B?

You should clearly state:

• associativity of ^ operator: 2^2^3 = 2^(2^3) or (2^2)^3?
• priority of unary - vs ^: -1^2 = -(1^2) or (-1)^2?
• x is only available in its own sum$, any sub expression using sum$ has its own scope of x

have been implemented

https://www.codewars.com/kata/reviews/5859b36dd3ed274f4e000692/groups/6450829210b72e000120b4d0

Kata author: it is not funny to randomly ban regex when your description also defines things in terms of regular expressions. In addition, this adds nothing to the task, besides making it more a nuisance. (If you think this adds "difficulty" to the task, then your kata is objectively bad. Find something better to author on.)

One can also argue that if you don't want people to use regex, then don't author the kata in Java and JS where regex is part of the language built-in. Author the kata in C++ or something instead.

Description contains a lot of wild tangents of the kata author contemplating about random stuff rather than a clear description of what is needed.

JS version is still stuck at Node v8.

Also, JS version doesn't have sample tests.

It returns the allowance remained after the correspinding month. (priceNewCar-priceOldCar+saving)

Since this is a duplicate (as mentioned before) it should probably be retired.

Duplicate issue. There is an open issue about it already, please don't open another about the same or comment there with your suggestion.

This (and iirc a lot of others as well) is a duplicate. Also it's not... worth it, in the sense that there's a built-in function for that, which you can and most people use on other ordinary Katas. It would be challenging if you restricted the use of built-in functions.

Hi,

yep it does, thx. This kata tho still suffer from the lack of random tests. If yu're still motivated to dig into that, just know that I began something there a long time ago... But I left it aside... :/
If ever that can help you (maybe not, tho...)

cheers

EDIT: I see you actually implemented some... I'd need to take a closer look (but not right now...)