Ta.

I suggest you do one thing: either parse the polynomial from a string, or find roots. ( I think both are duplicates though. )

Inconsistent return types is not good kata design. Find another way to signify infinite solutions.

Please use appropriate datatypes. The input should be a 3-tuple of numbers, not a string. Adding a secondary parsing task to the primary arithmetic one is not a good way to make a kata more interesting.
"Do one thing, and do it well."

Python, JS and Haskell have permuts(0) -> 1 test.

C needs updated example solution.

Approved with permuts(0)

JS translation

does not yet have permuts(0)

What makes you think there aren't?

( Python, possibly C )

Add a test for permuts(0) -> 1 ( because [] -> [] is valid ).

Or specify n > 0. But that's the chicken way out of course.

I love the irony of using show in the error case :D

Rounding is ( almost ) never the appropriate solution. If something's wrong, provide the problem, not the solution.

It is not related to that. Please ask Discord#reviewing why you should not be doing input validation.

You're thinking why your kata should exist. Please change your thinking to "what kata would add value to Codewars?"

Content should be novel, so if a task already materially exists, you should not be creating duplicates of it, especially not by adding unrelated additional tasks like input validation.

Please take any further discussion of this to Discord#kata-ideas.

Input validation has been done. Please provide only valid inputs.

This should be a translation on https://www.codewars.com/kata/5da74bf201735a001180def7 instead of a new kata.

Please unpublish this duplicate.