Hello everyone. Previously I was more of a Python programmer, but now I am trying to expand my knowledge of C++, so I am solving tasks in it more and more frequently. Today I experienced a strange issue with task [problem:1194C].↵
↵
The solution — [submission:57031662] — I wrote returned WA2, and no minor changes seemed to alleviate the problem (which cost me a lot of time). After 20 unsuccessful minutes of trying to zero in on the bug, I just coded the same thing in Python — [submission:57047262] — and it AC'd flawlessly.↵
↵
The specific test case I am getting an error on is the following:↵
↵
~~~~~↵
acefhjlnprtvxz abcdedfghijklmnopqrstuvwxyzabcdedfghijklmnopqrstuvwxyz abcdedfghijklmnopqrstuvwxyzabcdedfghijklmnopqrstuvwxyz↵
~~~~~↵
↵
"YES" is expected, whereas the program outputs "NO". However, the C++ submission answers this test case correctly when run locally, while giving another output on Codeforces.↵
↵
Could you please help me locate the problem? P.S. We are all human and prone to making mistakes, so I am not excluding the possibility that I missed something very obviously wrong.↵
↵
upd: Thanks. Problem solved. I was extremely stupid to miss such a thing.↵
↵
The solution — [submission:57031662] — I wrote returned WA2, and no minor changes seemed to alleviate the problem (which cost me a lot of time). After 20 unsuccessful minutes of trying to zero in on the bug, I just coded the same thing in Python — [submission:57047262] — and it AC'd flawlessly.↵
↵
The specific test case I am getting an error on is the following:↵
↵
~~~~~↵
acefhjlnprtvxz abcdedfghijklmnopqrstuvwxyzabcdedfghijklmnopqrstuvwxyz abcdedfghijklmnopqrstuvwxyzabcdedfghijklmnopqrstuvwxyz↵
~~~~~↵
↵
"YES" is expected, whereas the program outputs "NO". However, the C++ submission answers this test case correctly when run locally, while giving another output on Codeforces.↵
↵
Could you please help me locate the problem? P.S. We are all human and prone to making mistakes, so I am not excluding the possibility that I missed something very obviously wrong.↵
↵
upd: Thanks. Problem solved. I was extremely stupid to miss such a thing.↵
