It's Linux x64 NASM, so arguments are always passed in through registers rdi, rsi, rdx, rcx, r8, and r9, with any extra arguments pushed onto the stack. I've been using this reference sheet a lot while learning, this is more detailed instruction reference that's very helpful too.

Hi...

First, do not give up answers in your messages (that's why somebody already flagged it as spoiler, so nobody can now read it if he/she doesn't have already completed the kata. So much for helping people...)

Second, do not post "issues" where there are not. That was a flaw in YOUR code, not in the kata itself. If you have troubles, post a "question".

Third, "iissues" are used when a kata fails completely to execute, or when one can find a flaw in its logic. In either case you can/have to post an issue, but you have to document it too (just an information for future cases). So once again: troubles without demonstration of a flaw in the kata = "question". With demonstration = "ISSUE".

Fourth, when you stumble on a kata that has already lots of completions, there are far more chances that the flaw is in your ocde, not in the kata.

Fifth, ...but be aware that very old katas might contain some flaws that can't be corrected anymore, unfortunately... (test cases are locked after 500 completions), so if you find already 15 times the same isue in the discourses, it's useless to post it again...

With all of that, I hope you''ll have in mind some useful things to wander on CW and to use it the better wy (for everyone ;) )

Happy coding ;)