I found that, in the source code, there is some commented-out code. In general, it is a good practice to leave as few commented-out code as possible. Even if this issue is only very minor, I think that reducing the amount of commented-out code would greatly help to make the code clearer and cleaner.
I am ready to propose changes for that, but I don't want to remove code that should be kept because it contains useful information and/or backup.
Here is my opinion:
- Commented-out
print statements that were originally used to do print-debugging could be removed (even if they could be used to reactivate that debugging more quickly)
- Redundant code (commented-out code that is identical or very similar to non-commented one) should also be removed
I know that this issue is really nitpicking 🔍, and I apologise for that. But @ozekik could you please tell me your opinion on that matter? Do you think it is necessary to reduce commented-out code? If yes, which parts?
I found that, in the source code, there is some commented-out code. In general, it is a good practice to leave as few commented-out code as possible. Even if this issue is only very minor, I think that reducing the amount of commented-out code would greatly help to make the code clearer and cleaner.
I am ready to propose changes for that, but I don't want to remove code that should be kept because it contains useful information and/or backup.
Here is my opinion:
printstatements that were originally used to do print-debugging could be removed (even if they could be used to reactivate that debugging more quickly)I know that this issue is really nitpicking 🔍, and I apologise for that. But @ozekik could you please tell me your opinion on that matter? Do you think it is necessary to reduce commented-out code? If yes, which parts?