▲ | StopDisinfo910 a day ago | |
The personal dig was unwarranted. I apologise. > So, after reading code, one should write down what made him amazed and find out why it is so - whether it is a custom of a project or a peculiarity of code just read. Sorry but that’s delusional. The amount of people actually able to meaningfully read code, somehow identify what was so incredible it should be analysed despite being unfamiliar with the code base, maintain a list of their own likely error and self review is so vanishingly low it might as well not exist. If that’s the bare a potential new contributor has to cross, you will get exactly none. I’m personally glade LLVM disagree with you. | ||
▲ | thesz a day ago | parent [-] | |
List of frequent mistakes gets collected after contributions (attempts). This is standard practice for high quality software development and can be learned and/or trained, including on one's own.LLVM, I just checked, does not have a formal list of code conventions and/or typical errors and mistakes. Could they have that list, we would not have the pleasure to discuss that. That PR we are discussing would be much more polished and there would be much less than several dozens of comments.
You are making very strong statement, again. |