### wzw19991105's blog

By wzw19991105, history, 3 years ago,

I participate in codeforces round 578. But I received code coincide message from the system. Here are the links of two codes: 58583425 58592979 I admit these two codes looks very similarly. But I truly didn't cheat in the contest. The solution for that problem is just very simple. And we write similar code accidently. And I have tried many ways to contact Mike to recheck my solution. But till now I don't get any reply. I was told that Mike is very busy now. I completely understand. But for me, getting my rating up is very difficult. So I want to get my rating back. Can anyone give me some advice on recheck? Thanks a lot

• +15

 » 3 years ago, # |   0 Auto comment: topic has been updated by wzw19991105 (previous revision, new revision, compare).
 » 3 years ago, # |   0 are you seriously telling me a legit player would write "ggccdd". lol
•  » » 3 years ago, # ^ |   0 The second submission is mine, for the name "ggccdd",I don't know, He submitted before me,he got rated but I was not.
•  » » 3 years ago, # ^ |   +1 sorry , I am . just because I am afraid of having the same function name with the system function .
 » 3 years ago, # | ← Rev. 3 →   -6 Many math problems tend to have very similar codes. It is true.But next time, maybe you can add something (in code snippet) that only you will be able to produce?Like tons of header files and #defines, or some simple, but general templates (fastio), this may help distinguish your code.EDIT: I do not write this post to encourage cheating. Here is my version, you can see that it has nothing to do with cheating. It is just for distinguishing from other's code. My snippet... #include #include #include #include #include #include #include #include #include #include #include #include #include #include #if __cplusplus >= 201103L #include #include #endif using namespace std; #define pb push_back #define mp make_pair #ifdef GRAPH typedef pair Edge; #define v first #define w second #endif #if __cplusplus >= 201103L using ll = long long; using ULL = unsigned long long; #else #define ll long long #define ULL unsigned long long #endif #define lsh(i) (1 << (i)) #define lshll(i) (1LL << (i)) #define rep(i, n) for (int (i) = 0; (i) < n; (i)++) #define until(x) while (!x) #define fail(s) assert(!s) const int INF = 0x3f3f3f3f; const long double EPS = 1e-6; Snippet in action $\to$ 58661169
•  » » 3 years ago, # ^ |   0 That can be a good idea. Thanks a lot
•  » » 3 years ago, # ^ |   0 Maybe the people who give LilyWhite downvotes misunderstand him. His meaning is just that when coding for a simple math problem, you can add many #defines to distinguish from other's code so that you will not meet the situation like me now, but not mean encouraging anyone to cheat in the contest