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.
This comment is hidden because it contains spoiler information about the solution
This comment is hidden because it contains spoiler information about the solution
expected: [{:location=>"US", :id=>1, :name=>"Awesome Rubber Bottle", :price=>50.07, :card_name=>"Toni Senger II...ber=>"1234-2121-1221-1211", :transaction_date=>#<Date: 2012-07-29 ((2456138j,0s,0n),+0s,2299161j)>}]
got: [{:location=>"US", :id=>1, :name=>"Awesome Rubber Bottle", :price=>50.07, :card_name=>"Toni Senger II...ber=>"1234-2121-1221-1211", :transaction_date=>#<Date: 2016-07-24 ((2457594j,0s,0n),+0s,2299161j)>}]
That is the problem. We get 1 failure while submitting. There is no requirement for order by and I have tried both ASC and DESC, I get a different failure each time. Many of these US/EU sales based DB problems are poorly specified. There are hidden ordering requirements every where.
This comment is hidden because it contains spoiler information about the solution
This is still confusing.
Order by US then EU just means show the US orders first. The requirement needs to state to show them ordered by ID, US first then EU.
No, even as a native speaker it is quite vague. The wikipedia article helps a little but is still not clear.
This comment is hidden because it contains spoiler information about the solution
Even a stub of tests would be nice.
Mind the typos.
For clarity in dicussion. The following is the list in, the tree created, and the tree by levels result. Either buildTree needs to be fixed or the expectation that treeByLevels is the inverse of buildTree needs to change.
This makes lots of assumptions about the experience of the coder. The wikipedia link is not sufficient.
The supplied test case passes but the submit button never lights up.
Haskell language.
I had a hard time submitting this one due to a rendering/interaction bug. I am using Chrome on OSX. The pop-up note telling me how to submit was covering the "submit" button. The lower right corner would redraw and bounce around as I tried to click. I finally got lucky playing pixel whack-a-mole.