Equally, bash requires 'set -x' to not ignore errors. In both cases, the reasoning is significantly to do with backcompat, I believe. So, yeah, things that ha

Equally, bash requires 'set -x' to not ignore errors. In both cases, the reasoning is significantly to do with backcompat, I believe. So, yeah, things that have been around a long time often require a setting to be safe in cases that we, ten or twenty or whatever years on, consider common. Also: I did keep that in mind. That's why I started off suggesting using warnings, rather than (as I normally do for new code) making them fatal :)