Code Golf

Code golf, being about exploiting things, often brings about many questions about edge cases. Since we don't want each challenge to have to deal with all problems again and again, it makes sense to standardize some defaults for questions about various topics (including, but definitely not limited to, what's a valid answer, what are allowed I/O rules, what's a quine, a program, a language, etc).

Codidact has help topics, customizable by moderators, but we still need some way to create the standards in the first place.

Proposal

Meta gets a new tag, named "standards" (or "defaults"; if you have name suggestions, suggest them!), addable to questions by moderators.

Such meta questions discuss a single topic, with each answer being a separate suggestion. Depending on the type of question, either the best voted answer is the accepted standard (e.g. quine definition), or all answers above some certain threshold of votes (what specifically should that be?) is counted as a default (e.g. a single input or output rule, as there can be many).

Since it can be useful to post answers with the express intent of them being downvoted to signify that something is not acceptable, the answers on these questions shouldn't give reputation, if possible.

These posts could, afterwards, be linked in the help pages, tag descriptions, or wherever else applicable.

is a duplicate

This question has been asked before and has already been answered. It should be marked as a duplicate.

Please enter the URL of the proposed duplicate in the details field below.

not constructive

This question cannot be answered in a way that is helpful to anyone. It's not possible to learn something from possible answers, except for the solution for the specific problem of the asker.

Communities

Comments on How do we handle standardizing things?

How do we handle standardizing things?

Proposal

2 comment threads