3 ms·
Proving the non-existence of a proprietary source file somewhere that contains code which will become buggy with this experiment is impossible; we don't know al
by yencabulator 3y ago
Proving the non-existence of a proprietary source file somewhere that contains code which will become buggy with this experiment is impossible; we don't know all the source code in the world.
Proving the existence of a program that contains code which will become buggy is easy: share the code. Show actual program code, not a hypothetical; nobody is saying the experiment doesn't change behavior, people are saying it only changes behavior that doesn't matter to real world code.
On real world code discovered so far, the experiment would fix bugs.
- tapirl 3y agoYour logic is too illogical. It is the proposal's supporters' responsibility to prove the proposal doesn't do harm. If they are unable to do this, please don't pretend that this has been proven, and please just stop making any arguments. It is not my (and all other Go programmers') responsibility to do this. Here, I just shows the possibility that the proposal will do harm, and help others to find the broken cases easily. However, surely, Go programmers, in their spare time, can help the proposal's supporters to do this. But, again, it is strange that the proposal has been accepted before such attempts are made. :D, so weird. And, please read my tweets, there are several factors which are unrelated to finding broken code. In fact, the change will lead to more error-prone, instead of less error-prone.