News for hackers. Stuff that matters.
Re:Ruby 3.4, No More TypeError with **Nil as It Is Treated a... by kazinator on Tuesday May 14, 2024 @02:29AM (#40352230)
If you make something work which previously threw an error, it affects programs in which that error happens but is handled (whether by fluke or design).

One obvious example is a regression test case which confirms that the error is generated; that test now fails and must be removed.

It could sneak into an application.

They are just willing to crack those eggs to make their omelette.

Re:Ruby 3.4, No More TypeError with **Nil as It Is Treated a... by yunohn on Tuesday May 14, 2024 @05:23AM (#40353197)
That’s not breakage. It’s a canary test that should help you make the decision to remove your workaround code and related tests.