Comments

Why reject my awesome problems :(

+5

As a tester, I think this round will be educational and fun.

I think all the problems are great.

good luck!

good luck!

Bad problem ABC

-10

Do you know QQ?

When you findout some problems are same to some old problems, the participants may already findout it and start communicating. That mean, they may think little of this round and talk about other problems.

So I think the best way to solve the problems like problem of this round is inviting someone from different countrys and rateds to take part in the contest before it start and ban them in the official contest and pay them some money for doing this.

And if you aren't famous, your round will be unrated even you prepare it for half a year!

-20

But don't unrated this round will show people that if you have high status you can do anything you like and just say "NO! You guys are fucking wrong! I didn't mean to do it!".

-32

Since I am just a fucking Expert with fucking Low IQ, AQ and EQ and can be CM if this contest don't be unrated, I still want it unrated and stay at fucking Expert with my low IQ!

If you want to remove my account, welcome!

You, Your Team even the whole CodeForces will be well-known as tyranny!

+24

Since I am just a fucking Expert, I still have ability to give this fucking F a downvote.

-10

As my know, Mike removed some comments that have no problems but are bad for his team, is this on purpose or by accident?

+10

So why someone upvoited this post?

+11

Do you know QQ?

+19

I mean the problems like F that are well-known and can pass by copying the code from the Internet and make small(even no!) change.

My English is poor :(

+37

Can I always put on a well-known problem and say "I didn't mean to do it" ?

bad problem F

+32

Because of Codeforces Rounds are online, so we can copy the code from the Internet very quickly.

That mean, if you didn't know this problem before, you will get fewer points than people don't know how to solve but copy the code. It makes the contest unfair.

The pretest for A is too weak, I had just wrote a weird code and got a FST status :(

This will also bring wrong answer, for example:

int n=7; // (111)2
n+=n*2; // (111)2 + (1110)2 = (10101)2
cout<<n; // 21
int n=7; // (111)2
n|=n<<1; // (111)2 | (1110)2 = (1111)2
cout<<n; // 15

So bitwise operations are dangerous.

But this will cause more troubles than n*2.

good luck!

When you use n<<1 instead of n*2

int n=1;
n=n+n*2;
cout<<n; // 3
int n=1;
n=n+n<<1;
cout<<n; // 4

warning. and wrong answer

What do you mean? 这种网站你还想见到全中文的聊天?

Bad E, it is too common so that people who know kruskal reconstruction tree can pass it very fast but it is very diffcult to people who don't know this algorithm like me :(

Good C, it took me about 1 hour to guess the hidden conclusion :(