summaryrefslogtreecommitdiff
path: root/doc/data/messages/d/duplicate-code/details.rst
diff options
context:
space:
mode:
Diffstat (limited to 'doc/data/messages/d/duplicate-code/details.rst')
-rw-r--r--doc/data/messages/d/duplicate-code/details.rst10
1 files changed, 9 insertions, 1 deletions
diff --git a/doc/data/messages/d/duplicate-code/details.rst b/doc/data/messages/d/duplicate-code/details.rst
index ab8204529..07f5c72fa 100644
--- a/doc/data/messages/d/duplicate-code/details.rst
+++ b/doc/data/messages/d/duplicate-code/details.rst
@@ -1 +1,9 @@
-You can help us make the doc better `by contributing <https://github.com/PyCQA/pylint/issues/5953>`_ !
+If you need to make a change to the logic or functionality of the duplicated
+code, you will need to identify all the places that need to be changed, which
+can be time-consuming and error-prone. If there are multiple copies of the
+same code, then you will also need to test each copy to ensure that the
+functionality is correct. Duplicate code can be confusing for someone who is
+trying to understand the logic and flow of the code if they come across multiple
+identical or nearly identical blocks of code. The reader can then skim and
+think something is identical when it actually isn't. This is particularly true
+during review.