> I'm just a bit surprised that they devised this long path The original plan was to make the breaking change in 3.0, but that plan was canceled because it bro

> I'm just a bit surprised that they devised this long path The original plan was to make the breaking change in 3.0, but that plan was canceled because it broke too much code all at once. Hence why I proposed this multi-step plan to ease the transition. See the discussion on the tracker if you are curious: https://bugs.ruby-lang.org/issues/20205 https://bugs.ruby-lang.org/issues/20205