3 ms·
I actually find "bug" to be the most apt name for it. Their intent was to enable a feature, therefore writing it this way was not an error: it, however, did not
by prerok 3y ago
I actually find "bug" to be the most apt name for it. Their intent was to enable a feature, therefore writing it this way was not an error: it, however, did not take into account all the side-effects.
They did err on the side of caution, to protect the contributor, but when doing so, they did not take into account that it might be abused as well.
Just my two cents.
- dylan604 3y agoAt what point do you differentiate a bug from a design flaw? This reads like different devs were provided conflicting requirements that had no discussion between devs. It wasn't until after the branches were merged that the problem existed as the unit tests from each dev worked as expected.