• magic_lobster_party@fedia.io
    link
    fedilink
    arrow-up
    8
    arrow-down
    1
    ·
    1 day ago

    Notably, it refers to answers, not the invalidity or duplication of a question.

    I think it’s too much to close a question just because a different question happen to have the same answer. There might be a future answer that might apply to one, but not the other.

    • Kissaki@programming.dev
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      1
      ·
      1 day ago

      Do you think that applies to this question?

      Null coalesce operator vs comparison operator precedence? Both questions are about that. I don’t see one having a different answer to the other. In that case, duplication would only lead to spread out partially outdated information, instead of one place being updated.

      • magic_lobster_party@fedia.io
        link
        fedilink
        arrow-up
        2
        ·
        1 day ago

        Then it should be closed for being a duplicate question. I don’t think it makes sense to close any question for having a duplicate answer.