# | User | Rating |
---|---|---|
1 | tourist | 4009 |
2 | jiangly | 3823 |
3 | Benq | 3738 |
4 | Radewoosh | 3633 |
5 | jqdai0815 | 3620 |
6 | orzdevinwang | 3529 |
7 | ecnerwala | 3446 |
8 | Um_nik | 3396 |
9 | ksun48 | 3390 |
10 | gamegame | 3386 |
# | User | Contrib. |
---|---|---|
1 | cry | 164 |
1 | maomao90 | 164 |
3 | Um_nik | 163 |
4 | atcoder_official | 160 |
5 | -is-this-fft- | 158 |
6 | adamant | 157 |
6 | awoo | 157 |
8 | TheScrasse | 154 |
8 | nor | 154 |
10 | djm03178 | 153 |
Name |
---|
Normal: https://abc070.contest.atcoder.jp/ Beta: https://beta.atcoder.jp/contests/abc070
My first solution for D (which use recursive DFS) got RE, so I had to rewrite a non-recursive DFS solution in order to get AC. Is it because of the low stack size limit for Python?
A bit unrelated, but I want to ask Python user how do you deal with problems that require Balanced BST? There is nothing similar to set, map in C++, and it's definitely not a good idea to re-invent the entire thing under the constrained time of the contest.
The editorial defines a struct instead of make_pair():
The main benefit I see is that you can reference the components by meaningful name like ".cost" instead of ".second".
Is there any other benefit?
p.s. That new syntax of "using" versus "typedef" is also cool.