It seems that if the outer loop is over wishlist, then one doesn't need to check for uniqueness.

I'd like to suggest using some sort of spaced repetition algorithm (like what Anki or SuperMemo use) to make practicing old katas efficient. Spaced repetition is supposed to pick the right time for performing a given task, based on your feedback and previous repetitions. The core concept behind those algorithms is surprisingly simple.

Fixed the description.

This is to mimic the behavior of the normal Math.min function. My apologies, but the kata was locked before people brought up this issue.

Nice! can't wait. I just put this request in via the feed back dialogue. Loving the site.

We had the subscribe/unsubscribe featured planned but we have some other things to work on first. In the meantime I was able to make a quick change so that you stop receiving notifications once your comment is more than 5 days old (across all comment sections, not just feature requests).

They will be re-validated, when the test cases change. Sometimes you can see solutions at the bottom of the solutions page, which initially passed, but were invalidated later due to changed requirements / test cases.

The first version of this kata was solvable by only returning the names of those who accepted the invite, so i made some changes to the kata. Those solutions are for the older version of this kata.

Your solution should return the names of those who either accepted the invitation, or didn't respond to the invitation.
Hope that helps :)

Hi stampede. Great timing, Nathan and I were just discussing this today! We are in the middle of adding some large additions to the site and we wanted to squeeze this one in before those go out. We are planning to get favorites put in soon.

Thanks a lot dude! The real prize is knowing code warriors are enjoying my challenges :D

Yes, this function will return false, but the concept here is different. In the kata you take arguments as a whole, it could be one argument, it could be many, it could be none. But in your example there is no generalization, either value is a number or not. Calling isNumber() will just pass undefined to the value parameter, so it is indeed not a number.

In CoffeeScript or ECMAScript 6 grouping arguments is easier and more readable. Take for example this CoffeeScript snippet:

isNumberEven = (number) ->
  number % 2 == 0

areNumbersEven = (numbers...) ->
  numbers.every (num) -> num % 2 == 0

The way of dealing with arguments is important. A parameter with some value is something different than a parameter with an array of size 1 as a value.