New features are never added in maintenance branch.

And this feature has already been rejected multiple times in the past.

Looks like duplicate of at least #13657, #17267 & #19096.

Why? Is it too simply?

https://laravel.com/docs/5.6/helpers#method-dd

#13657 (comment)

I think that it's an added value. Otherwise why was this feature requested multiple times?

Count all the people shooting down those 4 requests and the lack of support for them from others 😉

@curry684
I'm sorry, I couldn't imagine that this feature can disturb the workflow of all these people 😉

It's code. It has to be maintained. It has to be documented. It's an attack vector.

Every line of code in a project is at some point going to be a burden on people managing the project.

"Code is not done when there's nothing left to add, but when there's nothing left to take away"

Now convenience functions are in themselves not necessarily wrong, assuming they're covering the 80+% use case (technically it becomes a facade then). In this case it most certainly doesn't, I can't remember typing die after a dump call more than a handful of times in the past years, because there's never a reason to - the dump shows up in the profiler toolbar, or in the template rendered, or on the command line. What's the added value of dying except in the handful of cases where you actively need to avoid subsequent code being executed based on the bug you're fixing? And which is, in a well architected structure, usually cleaner done by commenting that offending bit of code than just dying and shortcutting all system shutdown handlers, kernel termination handlers, mail spoolers and everything?

Still -1 for me.

👎 for me too. I am closing here as this was already rejected in the past and the core team still isn't convinced about the feature.

For reference, this is being reconsidered in #26970.