We've probably all seen new users ask questions with cumbersome I/O rules, like mandatory taking the input by reading separated lines of STDIN and outputting to STDOUT to give an example.
In those cases, we usually point them to the default I/O rules in the hope they'll change their challenge description, and also point to the Sandbox so they can get feedback on challenges before posting it on main next time.
However, what is the policy regarding answering those kind of challenges? If the challenge itself is completely clear, despite the cumbersome I/O rules, we should just downvote it. We don't have any reason to close-vote it as unclear if it really isn't, so that's not an option. But is there any reason to also keep it completely unanswered until they've changed their I/O rules?
The main reason I ask is because of this challenge that was posted yesterday. As you can see, it uses a similar input-format as programming contest websites usually use, which I will quote here:
- First Line: \$N\$(number of strings in the list)
- Next \$N\$ lines: String \$S_i\$
- Next line \$Q\$(number of questions)
- Next \$Q\$ lines : Three space-separated integers \$L\$, \$R\$ and \$K\$
Sample Input 5 aaaaa bbbbb ccccc ddddd eeeee 3 3 3 3 1 5 16 3 5 15
Very cumbersome, and even with mandatory 1-based indexing. Still, the challenge itself is clear.
I posted an answer for this challenge, which just got downvoted. Hence the reason for this meta question. I understand downvoting the challenge has a good reason, but what reason is there for downvoting the answers? If this score remains, I will just delete my answer no problem, but I'm mainly trying to understand the reason behind the downvote on my answer and how to prevent it in the future. And what people's opinion are regarding answering questions with cumbersome I/O rules.