> On 30 Mar 2017, at 15:59, William A Rowe Jr <[email protected]> wrote: > > I'd suggest we treat it as a bug, change the behavior accordingly in 1.6.0, > and @bug the API to indicate the old vs new behavior. Thoughts?
On reflection, +1 to all that. — Nick Kew
