Welcome to Codidact Meta!
Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.
Post History
It sounds like a feature of very limited use. I agree that it would be neat for Code Golf, where different answers are per definition of "different kinds". I don't really see any use for it on any ...
Answer
#1: Initial revision
It sounds like a feature of very limited use. I agree that it would be neat for Code Golf, where different answers are per definition of "different kinds". I don't really see any use for it on any other of the existing sites though. --- Regarding the specific example of C++ on Software Development, the tag policy is this: > Unless the question explicitly mentions which version of the C++ standard that is uses, the current active version of ISO 14882 is assumed (C++17). And very same "latest version unless you said anything else" policy can likely be assumed to apply for other languages too. This policy comes from SO where there was a very broad consensus in favour for it. This means that: - If a question is tagged C++ you are assumed to give an answer which will at least work in C++17 (even though it might not be optimal). In particular, it shouldn't use obsolete/withdrawn language features. - If the question is tagged C++ and C++11, you are required to give an answer that works in C++11. Giving one that only works in C++98 or C++17 etc would be off-topic. One might need to prompt the OP for details in case it matters. Generally, a good question is specific and unambiguous enough that there can't be multiple types of answers. --- I am particularly concerned for such an answer tag encouraging off-topic posts. Suppose you have a Q&A tagged C++. Then someone pops up out of the blue and posts "this is how you would do it in Java" and puts on a Java tag on their blatantly off-topic answer. We know from experience that this occasionally happens even without such a tag feature.