1. DO NOT use AI (or other machine tools) to translate your problem and/or solution. If you can't write in English, you cannot host a round on Codeforces. How will you answer hundreds of clarifications during the round?↵
↵
2. The proposal system doesn't support TeX (it's weird, but we'll have to work with what we have). Do not spam a lot of TeX. `\left( a + b \right)` is so much worse than `(a+b)`. Even `n <= 1e5` is better than `n \le 10^5`.↵
↵
3. If you open a proposal for review, it must have a solution. It doesn't matter if I can solve the problem or not, I need to make sure that you know how to solve the problem. If the solution is so obvious that it seems like a waste of time to write it: a) it shouldn't take much time then; b) should you propose this problem in the first place?↵
↵
4. Write the complexity of your solution.↵
↵
5. Write the limitations on all major parameters in the problem.
↵
2. The proposal system doesn't support TeX (it's weird, but we'll have to work with what we have). Do not spam a lot of TeX. `\left( a + b \right)` is so much worse than `(a+b)`. Even `n <= 1e5` is better than `n \le 10^5`.↵
↵
3. If you open a proposal for review, it must have a solution. It doesn't matter if I can solve the problem or not, I need to make sure that you know how to solve the problem. If the solution is so obvious that it seems like a waste of time to write it: a) it shouldn't take much time then; b) should you propose this problem in the first place?↵
↵
4. Write the complexity of your solution.↵
↵
5. Write the limitations on all major parameters in the problem.
