nice recursion

I think they forget to write code for others to read. If m jogs their short term memory that's good enough apparently

Using this solution you should worry about negative values, so it might be worth also checking for that

i started solving this and immediately my mind started thinking recursion idk why.

agree, nowhere close to best practice but the approach to for loop is worth learning

whats the point of r if n is equal to r? why not just use n alone?

Thats some fine recursion

I agree this is nowhere close to best practice

why do people not use descriptive variable names

r declaration is redundant in the first lines
recursive invocation should be placed as a last operand in return to reach tail recursion

i can mark it as clever,cause it simple, the simpler the better, but this is not the best practice

Brave!

simple and short.

Clever, but 'Best Practise'? Seriously?

1. Obscure naming
2. Obscure logic
3. No comments for obscure logic
4. Recursion
5. Formatting (blank line after last return)
6. 'm' variable is declared too far from it actual usage

Actually, it really may not compile due to project style violation rule like 'do not use single char names outside of lambdas'
(see lint)