PHP 8.5 adds pipe operator

Post by wraptile » Tue, Aug 05, 2025, 1:45 PM UTC

agos wrote: post #88

qwertox wrote: post #45

Earlier quoted context omitted.

I don't see how this is hard to reason about, assuming this is the resulting code when using variables: $tags = ...array_column($arr, 'tags'); $merged_tags = array_merge($tags); $unique_tags = array_unique($merged_tags); $tag_values = array_values($unique_tags); It also makes it easier to inspect the values after each step.

I don't think inspecting this is easier than adding |> IO.inspect() to a pipe chain

Post by sir_eliah » Tue, Aug 05, 2025, 1:58 PM UTC

avaq wrote: post #146

nilslindemann wrote: post #127

Earlier quoted context omitted.

Your simple example (`2 |> Math.sqrt`) looks great, but when the code gets more complex, then the advantage of the pipe syntax is less obvious. For example, foo(1, bar(2, baz(3)), 3) becomes something like 1 (2, (3 |> baz) > bar), 3 |> foo or (3 |> baz) |> (2, % |> bar) |> (1, %, 3 |> foo) That looks like just another way to write a thing in JavaScript, and it is not easier to read. What is the advantage?

Uhm, don't do it, then. That's like arguing that the addition of the ternary operator is a bad one because not all if/else blocks look better when translated into it. The goal is to linearlize unary function application, not to make all code look better.

Post by elif » Tue, Aug 05, 2025, 2:05 PM UTC

Post by Alifatisk » Tue, Aug 05, 2025, 2:18 PM UTC

Mystery-Machine wrote: post #188

PHP: $result = $arr |> fn($x) => array_column($x, 'tags') // Gets an array of arrays |> fn($x) => array_merge(...$x) // Flatten into one big array |> array_unique(...) // Remove duplicates |> array_values(...) // Reindex the array. ; // Ruby: result = arr.uniq.flatten.map(&:tags) I understand this is not pipe operator, but just look at that character difference across these two languages. // This comment was my $0.02…

    class Object
      def |>(fn)
        fn.call(self)
      end
    end

    result = arr
      |> ->(a) { a.uniq }
      |> ->(a) { a.flatten }
      |> ->(a) { a.map(&:tags) }

    class Object
      alias_method :|>, :then
    end

    arr
      |> :uniq.to_proc
      |> :flatten.to_proc
      |> ->(a) { a.map(&:tags) }

Post by epolanski » Tue, Aug 05, 2025, 2:21 PM UTC

gylterud wrote: post #192

dmead wrote: post #170

Earlier quoted context omitted.

Haskell seems pretty dead as well. Good think php has another option for line noise though.

What makes you believe Haskell is dead or even dying? New versions of GHC are coming out, and in my experience, developing Haskell has never been smoother (that’s not to say it is completely smooth).