Recently I prepared some problems and wrote a contest proposal which was submitted on $$$10^{th} July$$$. However, I haven't written any contests before, so I have some questions. Really appreciated if you can answer them.
$$$1$$$. How long does it take to get feedback from coordinators in average?
Today is $$$18^{th} July$$$. $$$8$$$ days has passed. It said that I will receive feedback in $$$2$$$~$$$14$$$ days, but I'm still worried. Although I believe the queue is not as big as two years ago, I'm afraid that I'll not be avaliable if the waiting time is too long （more than $$$1$$$ month)
$$$2$$$. Will I get notified if someone commented on my proposal?
$$$3$$$. Does Polygon support the $$$64$$$-bit version of C++17?
I didn't find it when I choose the language. One of my problems requires a checker which can compute even the number doesn't fit in $$$64$$$-bit integer, but under $$$128$$$-bit integer.
C++17 64bit supports __int128, which is the perfect one to use. However, if Polygon doesn't support that, I have to lower the constraints or manually implement bigint.
Thanks in advance.
You can choose language of a file when you click "add a file" or "add solution", check the list or langs there or just upload anything and see if it compiles.
Thanks for your answer!
Sadly, there's no option for
cpp.g++17-64 bits, butcpp.g++17and something like this.When I uploaded a file contains
__int128it didn't compiled successfully.1) I've asked to DeadlyCritic, he said that he got feedback after almost 5 months (the contest was Codeforces Round 652 (Div. 2))
(As mentioned by TheScrasse) For me it took almost 5 months, I also know some other people who had to wait 4-6 months to get feedback.
Yes, Mike will comment under your proposal, and you will be notified in Codeforces like a normal comment under your proposal.
I think no, it's not needed to think that much deeply into preparation part, more likely you should not start working on polygon before having a coordinator, otherwise the coordinator might reject a prepared problem. (I recommend being familiar with polygon, but no need to prepare the problems).
Is this really true? For some reason I was under the impression that they want to see prepared problems, not only statements.
It's what I know and seems reasonable to me. I prepared some of my problems before getting any feedback to get familiar with polygon, but there's no need to.
Problems don't have to be prepared already, you just need to provide statement and solution. It would be stupid to spemd a few hours and then getting the problem rejected because it's standard, boring or just doesn't fit the problem set.
5 months...That's very long :(
Anyway, thanks for your suggestions && answers