Translation has been rejected by someone, please propose a new fork and a new suggestion

This concept has potential but the execution flounders it

I took "no bad cases" to mean "I wont give you random shit like nulls and strings".

Should the description be updated then ( or now? ) as well? "no bad cases" ..?

https://www.codewars.com/kumite/665c22668c1787eb68874920

New fork

glovastefan It can be called a translation, a fork or a kumite, whichever you want to call it

Still, because the description was edited after I wrote this fork, it is causing a conflict and therefore can't be merged..

I suppose you could copy the description, sample and random test cases in your kata then reject this fork.

I will be back in around a week since I'm quite busy right now

It means that the description was changed while this translation hasn't been approved, causing the translation description to conflict with the current one.

This would require to update all languages, so not ideal. Also, users can train on how to write their own dictionary or hashmap that way!

Duplicate issue

In what language?

great feeling! on to the next challenge! go go go!

so much more, haha

That's because your solution is wrong, not because of floating point errors. Your solution calculates 9.45145... for starting_mark(1.52) for example then rounds it, when that's one of the supports of the linear equation and should give precisely 9.45 even before rounding. I'll post an algebraic derivation of the actual parameters in a spoiler'd comment below, but regardless this is not a kata issue.