# | User | Rating |
---|---|---|
1 | tourist | 3985 |
2 | jiangly | 3741 |
3 | jqdai0815 | 3682 |
4 | Benq | 3529 |
5 | orzdevinwang | 3526 |
6 | ksun48 | 3489 |
7 | Radewoosh | 3483 |
8 | Kevin114514 | 3443 |
9 | ecnerwala | 3392 |
9 | Um_nik | 3392 |
# | User | Contrib. |
---|---|---|
1 | cry | 167 |
2 | Um_nik | 163 |
3 | maomao90 | 162 |
3 | atcoder_official | 162 |
5 | adamant | 158 |
5 | -is-this-fft- | 158 |
7 | awoo | 156 |
8 | djm03178 | 155 |
9 | TheScrasse | 154 |
10 | Dominater069 | 153 |
Name |
---|
I think your recursion calls itself too much if you do it all in one go -
depee(10000000)
would calldepee(9999999)
which callsdepee(9999998)
...depee(0)
, and the program consumes alot of memory to keep track of all this recursion. Your second submission avoids this issue. Whendepee(n)
is called, it callsdepee(n-1)
which was previously solved, and thus fewer recursive calls need to be kept track of at a time.a great example why to use bottom-up if can(which we can here)
Thanks for your explanation, I get it now.