@dfhwze Thanks for sharing thoughts and reply/contribute to the thread. I'm thinking that what you suggested can be just a RAG app/component to get the job done, though it's still costly I think. Thinking of another cheaper solution IMHO can be to internally categorize katas by common known patterns. i.e PrefixSum, TwoPointers, SlidingWindowFixedSize, SlidingWindowVariableSize, Search, Sort, Merge, etc. Categories can contain sub-categories like Search can contain (BinarySearch, ExponentialSearch, FibonacciSearch, InterpolationSearch, JumpSearch, LinearSearch, TernarySearch, QuickSelectSearch) where sub-categories are attached by reviewers of katas during Beta period, then the system can report for authors whether the proposed kata is found within the provided category including its sub-categories.

Hopefully that makes some sense, I just find it doable, applicable, faster, cheaper, etc considering the trade-offs and the fault/error margin.

Best,

We should not enforce kata name standards, that would kill creativity. Instead, I believe a better option is to include a search AI assistant in the platform, one that can delve into descriptions of kata's and finds similar kata's for you. Not sure what the cost would be to implement such a feature though.

Please also note that there's provided Go Translation for this mentioned kata that's 3 years ago and still pending!
And there's no way "Or at least I do not know a way, yet" for me to catch a hidden similar kata like this using the search criteria provided prior to consuming time trying to present a similar one with some diffs. I'd rather have spent the time providing something really new and different or missing here on the platform. This "limited ability to find similar katas before authoring" happens because there's no standardized rules or protocol to force kata names/titles to represent something or maybe the search is for titles only not description or somethiing else I dunno tbh.

But I really spend a time searching to avoid duplication & rework before starting to author this. Now turns out that something a bit similar is available but thankfully not equivalent though :(

changed

Your dynamic solution is no longer working.

You are correct, i changed it Thanks

Yes :)

Done.

thank you!

I will design random tests.

The kata is not about bubble sort. Bubble sort is just arbitrary solution. Kata is about to implement your own sorting algorithm.

Yeah, I completely agree with this.

Yes,Even using the "toFixed" method does not solve the problem, and there is a bug in the test case.

Thanks for your feedback!

Covered all points. Pls check & LMK.

Regards,

Thanks dear, Check now please.
Random Tests are in-action..

Oops sorry, I didn't notice I made the same mistake twice in one line... SHOULD be fixed now...