Loading collection data...
Collections are a way for you to organize kata so that you can create your own training routines. Every collection you create is public and automatically sharable with other warriors. After you have added a few kata to a collection you and others can train on the kata contained within the collection.
Get started now by creating a new collection.
@angelplusultra
Distinct() keeps the first instance of an element and discards the rest.
The reason we reverse is because we want to keep the last item, not the first. A requirement from the kata description: "keeping the last ( rightmost ) occurrence of each element"
So we reverse it, remove the duplicates, then reverse it again to get it back to the original order.
This comment is hidden because it contains spoiler information about the solution
Thanks FArekkusu, I appreciate you making changes to alleviate these issues. :)
Sorry the Java author is @clcraig. Hopefully they will look into the issue shortly.
Ah, sorry FArekkusu! :)
Hey FArekkusu, are you able to look into dinglemouse's issue with your Java translation?
Cheers!
Thanks for the suggestion dinglemouse.
@FArekkusu is the author of the Java translation so hopefully they can jump in and fix this.
Approved :) thank you.
Still wasn't working, so rejected.
Thanks FArekkusu.
Upon trying to approve it I get the following error: "Description cannot be approved, recent changes from related record must be merged first".
Thank you FArekkusu, I appreciate everything that you've done.
Hey FArekkusu, I sincerely apologise.
I appreciate the time that you're putting in to fix this and thank you for the edits you've made.
I also apologise for being an amateur when it comes to programming, things that are probably simple or comon sense to you are still going over my head at this point.
I'm looking through your edits now, hopefully I'll be able to understand your changes. :)
Hey Voile, thanks again for all of the feedback, I really do appreciate you taking the time to help me.
The floating point issue should be fixed now I think?
Thanks again.
Hey guys, thank you for all the feedback and sorry for my rubbish tests.
I believe the tests should no longer have the floating point issue?
If I understand correctly, the floating point issue was because I was performing too many seperate calculations, with the precision getting worse and worse with each calculation?
Calculating the time in one statement was enough to fix the issue?
This comment is hidden because it contains spoiler information about the solution
Loading more items...