Nicolas Grekas

I considered this @derrabus but I don't see any smooth upgrade path to make it happen. Do you have one in mind?

Actually, I just realized that `$catch` and the new behavior are not entirely connected. If you look at the code, we *always* catch exceptions, even if `$catch` is `false`. When...

Any other input here? I don't want us to release the deprecation if that's not what we want.

> enum CatchThrowables About this proposal, I'm not convinced it makes sense: exposing the behavior as public API doesn't look desired to me as the difference is too subtle. Better...

After talking with ppl in the core-team, I updated the implementation: - the new argument on HttpKernel is back, but it's named handleAllThrowables since we discovered that's a more appropriate...

Basically yes. We also remove `Test\ExceptionSubscriber` because `$client->catchExceptions(false);` already exists and works great for the need.

Thank you all for the review!

That'd make sense to me, we should display them as we do for `\n`, as eg `\u{feff}`

Unless I missed something, this would be very unsafe. If a tag expires before the items that are bound to it, said items won't be deleted when the same tag...

Thanks that for the details. The issue with adding an expiry to tag items is that Redis will flag them as volatile, which means they could be evicted while their...