PHP 8.5's pipe operator and the array stdlib problem

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant

delacry · 2026-04-30 · via DEV Community

PHP 8.5 shipped a pipe operator, from <a href="https://wiki.php.net/rfc/pipe-operator-v3" rel="noopener noreferrer">Larry Garfield's RFC</a> (approved 33-7). The marketing examples look great: <div class="highlight js-code-highlight"> <pre class="highlight php"><code>$slug = $title |> trim(...) |> strtolower(...); </code></pre> </div> Reads top to bottom, no nesting, types flow. For chains of single-input transformations, which is what the RFC was explicit about targeting, the operator does exactly what you'd want. The friction starts when you reach for it on PHP's array stdlib, which is where most day-to-day chaining happens. Most of what follows isn't really a flaw in the pipe operator itself. It's the stdlib's call-shape inconsistencies leaking through whatever composition mechanism you put on top of them. <h2> The naive port </h2> A common form-handling task: clean user-submitted tags and sort a-z. <div class="highlight js-code-highlight"> <pre class="highlight php"><code>$cleanTags = array_values( array_filter( array_map(fn($t) => strtolower(trim($t)), $rawTags), fn($t) => strlen($t) >= 3 ) ); sort($cleanTags); </code></pre> </div> Three nested calls plus a trailing <code>sort</code>. It has to be its own statement because <code>sort</code> returns <code>bool</code> and mutates the array by reference. You read the nested part middle-out: <code>array_map</code> runs first, then <code>array_filter</code>, then <code>array_values</code>. Eyes parse opposite to execution. The pipe operator should clean this up. Here's the rewrite: <div class="highlight js-code-highlight"> <pre class="highlight php"><code>$cleanTags = $rawTags |> (fn($ts) => array_map(fn($t) => strtolower(trim($t)), $ts)) |> (fn($ts) => array_filter($ts, fn($t) => strlen($t) >= 3)) |> array_values(...) |> (function ($ts) { sort($ts); return $ts; }); </code></pre> </div> Better than the nested version. Reads top to bottom. But three things are happening here that the toy examples don't tell you about. <h2> Gotcha 1: argument-order mismatch </h2> <code>array_map</code> and <code>array_filter</code> take their arguments in different orders. <div class="highlight js-code-highlight"> <pre class="highlight php"><code>array_map(callable $callback, array $array, ...); // callable first array_filter(array $array, ?callable $callback, ...); // array first </code></pre> </div> The pipe operator passes the left value as the first argument to whatever's on the right, so you can't first-class either function into a chain: <div class="highlight js-code-highlight"> <pre class="highlight php"><code>$result = $rawTags |> array_filter(...); // works, array is first arg $result = $rawTags |> array_map(...); // broken, $rawTags lands as callback </code></pre> </div> To use <code>array_map</code> in a pipe, wrap it in an arrow function to swap the argument order. In the rewrite, both <code>array_map</code> and <code>array_filter</code> need a wrapper. <code>array_map</code> to swap arguments, <code>array_filter</code> to inject the predicate. Only <code>array_values</code> fits naturally because it's single-argument. The pipe operator doesn't paper over the stdlib's inconsistencies; it makes them more visible. Every chain across <code>array_map</code> / <code>array_filter</code> / <code>array_reduce</code> ends up with this kind of glue in it. <h2> Gotcha 2: arrow functions need parentheses </h2> Look at the wrappers in the rewrite: <div class="highlight js-code-highlight"> <pre class="highlight php"><code>|> (fn($ts) => array_map(fn($t) => strtolower(trim($t)), $ts)) </code></pre> </div> The parens around the arrow function are required, not stylistic. Without them, the arrow function "captures" everything to the end of the expression: <div class="highlight js-code-highlight"> <pre class="highlight php"><code>$result = $rawTags |> fn($ts) => array_map(...) |> array_values(...); </code></pre> </div> The parser reads that as the arrow function returning everything from <code>array_map(...)</code> through <code>|> array_values(...)</code>. One stage, not two. This was the edge case the 2025-08-28 RFC errata pinned down. The rule: wrap arrow functions in parens any time they appear in a pipe chain. Forget once and the bug is silent. First-class callables (<code>trim(...)</code>, <code>strtolower(...)</code>) avoid the issue because they're a single token, with no expression body for the parser to grab. The moment your chain has any non-unary stdlib function, though, you're back to writing <code>(fn($x) => ...)</code> over and over. <h2> Gotcha 3: by-reference functions don't compose </h2> That last step in the rewrite is uglier than the others for a reason: <div class="highlight js-code-highlight"> <pre class="highlight php"><code>|> (function ($ts) { sort($ts); return $ts; }); </code></pre> </div> It can't be a one-liner arrow function, and it can't be a first-class callable. The RFC explicitly forbids first-class callables for any function whose first parameter is by-reference, which takes a long list of stdlib functions out of the pipe-able set: <div class="highlight js-code-highlight"> <pre class="highlight php"><code>$rawTags |> sort(...); // error: by-ref param $rawTags |> array_walk(...); // same $stack |> array_pop(...); // same </code></pre> </div> <code>sort</code>, <code>rsort</code>, <code>usort</code>, <code>ksort</code>, <code>array_push</code>, <code>array_pop</code>, <code>array_shift</code>, <code>array_unshift</code>, <code>array_walk</code>. All by-reference, all rejected. Most of the in-place array operations you'd reach for during a chain. The workaround is the full closure shown above: a function that mutates and returns. In practice you'll usually call <code>sort</code> outside the pipe and feed the result in. <h2> Where the pipe operator actually shines </h2> For chains of unary stdlib functions, the operator is exactly what you'd want: <div class="highlight js-code-highlight"> <pre class="highlight php"><code>$slug = $title |> trim(...) |> strtolower(...) |> (fn($s) => preg_replace('/[^a-z0-9]+/', '-', $s)); </code></pre> </div> <div class="highlight js-code-highlight"> <pre class="highlight php"><code>$payload = $body |> json_encode(...) |> gzencode(...) |> base64_encode(...); </code></pre> </div> Top to bottom, no argument-order gymnastics, the parens-around-arrow rule isn't a constant tax. String pipelines, encode/decode chains, math chains, hex round-trips. Anywhere the data is the first argument and the functions are unary, this is good code. <code>__invoke</code> objects and instance methods compose cleanly too, which is probably the use case the operator was actually designed for. <h2> A coherent collection API does this naturally </h2> The same tag-cleanup code with a collection library: <div class="highlight js-code-highlight"> <pre class="highlight php"><code>$cleanTags = listOf($rawTags) ->map(fn(string $t) => strtolower(trim($t))) ->filter(fn(string $t) => strlen($t) >= 3) ->sorted(); </code></pre> </div> No wrappers, no parens-around-arrows, no <code>array_values</code> plumbing, no by-ref dance. PHPStan carries <code>ImmutableList<string></code> all the way through. <code>map()</code>, <code>filter()</code>, and <code>sorted()</code> are methods, so the data is implicit (it's <code>$this</code>) and the callable is the first explicit argument every time. The example uses <a href="https://noctud.dev" rel="noopener noreferrer">noctud/collection</a>, which is what I work on. Other collection libraries (illuminate/collections, doctrine/collections, ramsey/collection) solve the call-shape problem the same way at the method level. The point isn't the specific library; it's that a coherent method-chain API sidesteps the inconsistencies the pipe operator inherits from the stdlib. <h2> The real fix would be native </h2> The deeper issue is the stdlib itself. PHP's stdlib was never shaped for chaining. <code>array_map</code> and <code>array_filter</code> taking arguments in different orders is a 1995 design that calcified before anyone thought about composition. The pipe operator works around the symptom. Native methods on arrays and strings would fix the cause. Nikita Popov's <a href="https://github.com/nikic/scalar_objects" rel="noopener noreferrer">scalar_objects extension</a>, from 2014, already showed what that could look like: <code>$str->length()</code>, <code>$arr->map(...)</code>, methods directly on the primitives. It worked, and it's been sitting there as a proof of concept for over a decade. The reason it never made it to core is that as an extension, every userland library could register its own method set on the built-in types, trading the current inconsistency for a different one with composer-install collisions on top. Doing it there means making the harder calls extensions get to dodge: which methods, what's the receiver, and the bigger question of whether <code>array</code> is really one type or two (a list and a map) wearing the same hat. Most modern languages split them. PHP didn't, and userland libraries (noctud/collection included) only paper over that conflation from outside the language. If core ever takes a serious run at native methods on arrays and strings, plus the harder design call of splitting <code>array</code>, that's the win the pipe operator alone can't deliver. <h2> The takeaway </h2> PHP 8.5's pipe operator is a real improvement. Use it for unary chains: string normalization, encode/decode pipelines, math, hex round-trips, pipelines of <code>__invoke</code> objects. For array operations (anything involving <code>array_map</code>, <code>array_filter</code>, or by-reference functions like <code>sort</code> and <code>array_walk</code>), the operator inherits all of PHP's stdlib inconsistencies and adds an arrow-function-paren footgun on top. More readable than the nested version, but the readability gain shrinks once you've added all the wrappers. If your code spends most of its time chaining array operations, a collection library remains the cleaner answer.

此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。原文来自 — 版权归原作者所有。

推荐订阅源

DEV Community