After the World Final this year, I think that instead of let the reference material we used rot in a depository, it is better if we can collaborate and polish a piece of reference that can serve as the foundation for any team that wishes to best their skill in contests, or for any person who wishes to achieve a higher rating on Codeforces. After all, who can say that they haven't thought of "color their name red" on this website?
So here it is, Allow me to present you Luna's Magic Reference, which is the foundation we used to develop our reference for the ICPC contests last year: https://github.com/Nisiyama-Suzune/LMR
I hope that you can try to utilize it in the next contest, point out bugs or confusing parts if you find any, and share your own masterpiece of code that can potentialy benefit the whole community.
Thanks in advance and wish you all high rating!
Auto comment: topic has been updated by Nisiyama_Suzune (previous revision, new revision, compare).
Auto comment: topic has been updated by Nisiyama_Suzune (previous revision, new revision, compare).
Who has taught you to put the closing curly bracket on the last line of code block? It is the worst possible codestyle. Completely unreadable.
If you think you need to read your ICPC libraries, you're best off not using them. The whole point is that you're typing out complex code without thinking to save time.
Also, it saves space.
It is more about compressing the code to fit in the page limit in a typeable and checkable style than to read it, since you only need to type/copy-paste it during the contest anyway.
Actually, reading, checking and understanding the code in the reference should be done before a contest, when you have plenty of time to refactor the code and get familiar with it. Much time is unnecessarily wasted should you have to read or question a code in the reference during a contest.
...Or if you run short on preparation time, just figure out the interface and forget about the implementation. You only need to type it or copy-paste it during the contest anyway, which, of course, does not need readability at all.
I do agree it is the worst code style though, but just think about the 25-page limit of the World Final. :)