On Fri, Dec 28, 2012 at 8:34 AM, Peter Rabbitson <rabbit+p5p@rabbit.us> wrote: > Is there any word on this issue? I just hit this bug in reverse[1] and > while there is ample discussion about it being a problem I see the same > behavior under current blead. Is there a chance *at least* for a warning > to be added so that it lands in 5.18? The process kind of fizzled somewhere. I'm in favor of a warning in 5.18, see attachment. LeonThread Previous | Thread Next