Hi Richard,
Is it OK to throw a hard error for this? Maybe the rules are different from C and C++, but normally we can't do that for code that's only invalid if executed. An unconditional warning would be good though.
I can also issue an unconditional warning; this will even simplify
the code somewhat. Actually, we do the same for simple out-of-bounds-
accesses, so this would be consistent.
I'll rework the patch accordingly, unless somebody else speaks up
with another idea.
Regards
Thomas
