# | 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 | 166 |
2 | maomao90 | 163 |
2 | Um_nik | 163 |
4 | atcoder_official | 161 |
5 | adamant | 160 |
6 | -is-this-fft- | 158 |
7 | awoo | 157 |
8 | TheScrasse | 154 |
9 | nor | 153 |
9 | Dominater069 | 153 |
Name |
---|
My solution seemed to be a little bit too slow, so I’ve tried to squeeze it. Bitsets were used only to store the matrix, so I’ve tried to check if asking about an edge will be faster on normal array. Finally, the only differences between the first and the last submission are some optimizations in the top of the code. I didn’t care about incorrect attempts, as the wouldn’t change my position.
My debug does nothing without an exact compilation flag. You might remember it from a puzzle for viewers from the last ICPC finals.
Thanks, that explains everything! And I guess you were submitting to the actual contest instead of using the "run" function to compare the time spent on pretests between different solutions?
Yep, exactly. I knew that my penalty wasn't great so I just wanted to make sure that E passes.
orz gennady