Switched

switch the title to Weight Guide or Weight Assistant

With the nibbles and arbitrary lengths of results, whis does not seem to be a clear duplicate indeed.

To risk sounding like a not real programmer, I honestly admit I never encountered two's complement with non-fixed width representations. All my experiemce with the topic boils down to constant width 32- or 64-bit values, and this probably impacts my understanding of the topic for values which can be arbitrarily extended to the left.

What can I say other than "smarter every day!" and thank for the lesson :)

"MSB functions as a sign bit" is ( at least an implied ) part of the definition. The bytes / nibbles thing then tells you whether or not to tack on an extra nibble.

Of course it is possible to spell out everything, but you probably know what I think of spelling out everything.

At the risk of calling you not a real programmer, I think a real programmer may be expected to know and understand two's complement well enough that it shouldn't be necessary to give a full definition of it. And unreal programmers can go read Wikipedia; that's what it's there for.

Changed inner @describe to @it and add some fixed tests to submission tests.

Tests are structured in an incorrect way:

• calls to assertions should be placed in a function decorated with @it. Assertions inside of @describe are not valid. Most probably you should change the inner @describe to @it.
• Submission tests should have fixed tests too. Fixed tests could be the same as your example tests, but with failure messages showing inputs.

Thanks :D

already fix it

It's simular, but not duplicate.

    test.assert_equals(assistance(0), "Error", "Not right!"), 
    test.assert_equals(assistance(20), "Nothing to hang", "Not right!"), 
    test.assert_equals(assistance(22.5), "Error", "Not right!"), 
    test.assert_equals(assistance(25), "Only lock", "Not right!"), 
    test.assert_equals(assistance(30), "1 orange, lock", "Not right!"), 
    test.assert_equals(assistance(35), "1 black, lock", "Not right!"), 
    test.assert_equals(assistance(50), "1 green, 1 orange, lock", "Not right!"), 
    test.assert_equals(assistance(65), "1 blue, lock", "Not right!"), 
    test.assert_equals(assistance(100), "1 red, 1 green, 1 orange, lock", "Not right!"), 
    test.assert_equals(assistance(102.5), "1 red, 1 green, 1 orange, 1 white, lock", "Not right!"), 
    test.assert_equals(assistance(103), "Error", "Not right!"), 
    test.assert_equals(assistance(345), "6 reds, 1 green, lock", "Not right!"), 

On these 12 sample tests on python it says "Not right". Is this supposed to be in this kata?

Thanks, i described this case.

Duplicate?

https://www.codewars.com/kata/6400c3ebf4a0b796602988a6
https://www.codewars.com/kata/6400caeababb193c64d664d1

I see, but then I would say that this should be a part of the spec, and not example.

For weight of 105kg, there are two possible answers:

• bar + (red + yellow + lock) per side, or
• bar + (blue + blue + lock) per side.

It is not clear if the "The heaviest pancakes are always hung at the beginning, and the lightest pancakes are hung at the end" describes just order of the plates, or does it also explain the way of choosing them.