I found quite a few, you arrogant dutch-man:

• The example shows the quota as a ceiled integer, is that for display purposes or hidden spec that we need to ceil total votes over total seats?
• You don't explain which method of "highest average of votes per seat" to use. Only in the wiki page there is a reference to the method used in Dutch elections. I'm not even sure you use that one.
• You don't explain whether continious updates of seats should be used in assigning residual votes, or a snapshot should be taken a priori, both in first phase, as in recalculation of seats in coalitions.

hm... didn't think that such a simple pattern would work. but okay i guess.

It should be fixed.

Try again with your previous code, close the issue if it is fixed.

Probably, because your current code works and doesn't mutate the input array.

Some of the random testing in JS seems a bit off.

  ["w","8","k","g","s","3","4","m","1","V","D",
   "r", // <--
   "A","L","t","u","l","n","E","z","q",
   "r", // <--
   "Y","F"]
   
   ["Q", // <--
   "0","g",
   "Q",  // <--
   "3","q","m","n","9","L","W","9","Z","H","e","J","g","I","a","n","B"]

Expected: false. Actual: true.

Not sure if it could be related to the same input modification issue that another user mentioned regarding Python,
as my solution does modify the items input array.

performance issue fixed

fixed

fixed

You don't want to be patronized?

I tried very very hard to understand what you do not understand. Everything is written down. What is not to understand about the line below? Is it maybe the word 'standard' that you read as 'allocation of seats excluding residual seats'? No clue, the sentence below talks about 'standard allocation' as opposed to 'allocation within combination'.

'A combination is treated as 1 party but after the standard allocation the seats gathered by the combination need to be allocated again to its individual members.'

Keep opposing bad specs! You will not find them in this kata.

Don't patronise me, in my long career I've always challenged bad specs.

Everything you need to know is in the description. Just read better. From my 30 years of experience that is sometimes hard for developers (also when I read the comments here).

And yes, kata is hard. I did the kata myself too and had a problem with it.

Enabled in this fork

Yeah, this description is a pain. Also allocating the remaining residual seats after combinations have been handled is a complete mystery. I wanted to solve this kata out of loving memory for Pim, but F it, just not worth it.