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.
Got it, thanks!
Thanks for explanation, but I still don't get it. It is writen " This defect shows up in all positions (ones, tens, hundreds, etc)." So, in my example, for 15350 3 in hundreds changes to 5 and we get 15500. Aga, seems like I miss something here.
Hi, I don't quite get how the odometer shows 15339 if it skips 4s. According to the description the odometer should go from 15229 immediatly to 15500. What do I miss?
It is not clear from the description when to throw an exception from undo and when just to return? For example:
1.Throw an exception after undo, get, undo:
unRe.undo();
Test.assertEquals(unRe.get('y'), 2, 'The undo method restores the previous state')
try {
unRe.undo();
Test.expect(false, 'It should have thrown an exception');
2.Shoud retun after undo, get,get, undo:
For "Random true multidimetional tests" in 99.9% I get "Expected: true, instead got: false", but when I write console.log(arr) in 100% of cases I get
arrays with numbers that are not squares. Seems like something wrong is here.
Thank you for the answer, but still don't understand. Personally I don't use log function in my code. And any call to call function handels by my custom Function.prototype.call.
Guys, could somebody tell please is the following error is relevant or kata is broken?
console.log("" + this.format(_message(Test.trace(ex)) ^
TypeError: Object # has no method 'log'
This is strange but when i run your code I get for compareVersions("11", "10.1") false instead of true and the same for compareVersions("10.4.6", "10.4.1.9")
I don't quite understand what does it mean "handler functions can subscribe and unsubscribe handlers, but the changes should only apply to the next emit call - the handlers for an ongoing emit call should not be affected"? Coould you please give an example?