On Mon, Jun 20, 2022, at 12:58, Dave Mitchell wrote: > In conclusion: > > 1) we can't do nothing, and the longer we leave it the worse it gets. > > 2) I think it is better to have a break where smartmatch/when() is a > compile-time error for a few releases before introducing a new smartmatch > with radically different behaviour, rather than just switching to the new > behaviour with no gap. > > 3) I am not opposed to a further deprecation cycle (possibly with a new > mandatory warning), before we disable it. Surprising no one, this is my position also. I would be delighted to put in a straight up "smartmatch is deprecated and will be removed in v5.X" basically today. I have wanted to rip this thing out almost since it got put in. -- rjbsThread Previous | Thread Next