I have a few friends who write rounds in Python, and I noticed that they don't use some very simple optimizations, and the program ends up getting TL. Meanwhile, if you use these constructions, in half or more cases TL is removed.
First,
# | User | Rating |
---|---|---|
1 | tourist | 4009 |
2 | jiangly | 3773 |
3 | Radewoosh | 3646 |
4 | ecnerwala | 3624 |
5 | jqdai0815 | 3620 |
5 | Benq | 3620 |
7 | orzdevinwang | 3612 |
8 | Geothermal | 3569 |
8 | cnnfls_csy | 3569 |
10 | gyh20 | 3447 |
# | User | Contrib. |
---|---|---|
1 | awoo | 161 |
2 | maomao90 | 160 |
3 | nor | 157 |
4 | atcoder_official | 156 |
4 | cry | 156 |
6 | -is-this-fft- | 155 |
7 | maroonrk | 154 |
8 | adamant | 153 |
9 | Um_nik | 151 |
10 | djm03178 | 146 |
Some easy but useful optimization in Python.
I have a few friends who write rounds in Python, and I noticed that they don't use some very simple optimizations, and the program ends up getting TL. Meanwhile, if you use these constructions, in half or more cases TL is removed.
First,
Rev. | Lang. | By | When | Δ | Comment | |
---|---|---|---|---|---|---|
en8 |
![]() |
Dart-Xeyter | 2020-10-31 22:48:44 | 9 | Tiny change: ' is quite strong).\n\n~~~~' -> ' is quite a lot).\n\n~~~~' (published) | |
en7 |
![]() |
Dart-Xeyter | 2020-10-31 22:40:40 | 23 | Tiny change: '1] from a recent round. This cod' -> '1] from a [problem:1413B]. This cod' | |
en6 |
![]() |
Dart-Xeyter | 2020-10-31 22:36:43 | 33 | ||
en5 |
![]() |
Dart-Xeyter | 2020-10-31 22:34:39 | 907 | ||
en4 |
![]() |
Dart-Xeyter | 2020-10-31 22:25:09 | 1204 | ||
en3 |
![]() |
Dart-Xeyter | 2020-10-31 22:07:55 | 1158 | ||
en2 |
![]() |
Dart-Xeyter | 2020-10-31 21:53:34 | 1349 | ||
en1 |
![]() |
Dart-Xeyter | 2020-10-31 21:24:14 | 285 | Initial revision (saved to drafts) |
Name |
---|