| # | User | Rating |
|---|---|---|
| 1 | Benq | 3676 |
| 2 | jiangly | 3670 |
| 3 | Kevin114514 | 3657 |
| 4 | maroonrk | 3355 |
| 5 | Um_nik | 3353 |
| 6 | squareOf105 | 3346 |
| 7 | tourist | 3343 |
| 8 | strapple | 3324 |
| 9 | heuristica | 3322 |
| 10 | jiangbowen | 3291 |
| # | User | Contrib. |
|---|---|---|
| 1 | Qingyu | 158 |
| 2 | nik_exists | 150 |
| 2 | maspy | 150 |
| 4 | AmShZ | 143 |
| 4 | Um_nik | 143 |
| 6 | Errichto | 139 |
| 7 | adamant | 137 |
| 8 | BledDest | 134 |
| 9 | maroonrk | 133 |
| 10 | qwexd | 130 |
|
+22
Is it just me or does anybody realise that problem B has a rick roll in it? (Yeltsa Kcir is Rick Astley reversed) XD |
|
0
I saw the update in the editorial. Thanks for explaining it! |
|
0
Thanks for the fast editorial. For problem C, may I ask that how do we find the two required edges to break the tree into 3 parts with xor sum of each component equal to x in O(n) or O(n lg n) time? I have been trying to solve this problem but I am stuck at the implementation. |
|
0
Also, beside the problemset, the editorial is not easy to understand... I really don't get how does the word "group" mean in div2D/div1B. Would somebody explain it? |
|
0
Instead of blaming the weak pretests, as opposed to test 38 of problem C (which I failed too), why not think about the coding mistake we make? If you think programmers can simp, you are overestimating them. |
|
0
The honest word is, I need to improve. Nothing else. |
|
+5
Don't blame yourself. The difficulty of the problems is not a problem. The difficulty only reflects that we have a lot to learn, which is not your mistake at all. Thanks for the meaningful questions! |
