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.
That's a great move right here! well done !!
its called aliasing..
number_to_string = str
its like instructing python that str has another name as well, namely 'number_to_string'.
Thanks for the detailed explanation of this approach.
Dayum thats a smart move
Thanks for the explanation!
outstanding move!
How does this work ?
Link for ranked list is 404. Any list anywhere that shows the ranking independent of honour?
Thanks bkaes. Thats looks like it is the case.
print '...'
is either Ruby or Python, but the error message showsnode.js
. Did you accidentially switch languages?Add some remarks/notes/details about the translation process to the docs. The current translation box states
However, there were some questions about approval by kata authors, and AFAIK only moderators can approve translations at this point.
Display the date of a kata creation
Everything was working well up until an hour or so ago when I started to get this error for anything I try to submit
http://i.imgur.com/NRnJb5h.png
It seems that "Preloaded" module isn't loaded when user presses "Run tests" (at least, for Haskell). But it is loaded when user submits solution.
So I cannot, for example, define data types or some instances in this module
Also this problem isn't detected in kata validation process
I think that correct behavior is to load it in both cases. Please explain me design goals if I'm wrong. Also validation should run tests (the same way as when user presses "Run tests") with complete solution.
For Pyhton problems, on submission, if an error occurrs the line number for the error is wrong. My guess is that the offset comes from a bunch of lines that are implicitly being added at the top of the script before compilation. This also leads to not being able to use
from __future__ import x
statements cause they need to be at the top of module, but at the top of the module there are the implicitly added lines.Loading more items...