Interesting approach. Not very readable but I still kind of like it.

very good, my codig is same.

Got it, I did not know that. Thank you very much for teaching me this. When I Re-publish this kata I will fix that.

Handling money with software is generally a difficult and challenging topic. There is a couple of ways to do this: data types with decimal representation, fixed point data types, integers, depending on exact requirement and design. But double and floating point types are very inappropriate for such tasks.

Due to all of the issues in this kata, I am going to Un-publish this kata and publish it again when it is fixed. I will Un-publish this kata soon.

That is very strange. I will try to fix that.

I get this expected: <40.160000000000004> but was: <40.16>, expected: <477.4599999999996> but was: <477.46000000000004>.

True. Will fix that soon.

I am sorry, what should I use instead of "double" to represent money?

1.) I am sorry if it is not satisfying. I need to step up my skills and make some challenging katas.

2.) You are right, I took that out. I just wanted people to give feedback so that I can improve on my skills.

3.) Sorry, I really need to be a lot more creative with the kata names.

Thank you very much for your feedback.

Okay, that is a good point. I will try to create better katas in the future that are actually challenging. Thank you for your feedback.

• On top of my previous issue, it's again just a bunch of compilation errors and just a one or two actual bugs in the logic. Some might find it fun tho.
• The "VOTE ME PLX" note is longer than the description itself. Is it relly needed?
• Titles like "Kata series: #1", "Kata series: #2", ... tend to be problematic and are discouraged, because when some kata get approved, some kata get retired, and some stuck in beta, all the users get is "Kata series #7" and nothing more.

THE BUG with the kata is that it requires use of double to handle monetary values.
Using floating point data types to represent money is bad. Tests should test for it.

The task is to find two bugs and fix 6 compilation errors. I am not sure whether fixing compilation errors constitutes a good bug fixing kata. All you need to do to fix them is to follow red squiggles in your IDE.

My "attempt" that passed should be a call for additional testing.