PHP Wiki

deprecations_php_8_7 - add b prefix deprecation proposal from mailing list

daniels (daniels@undisclosed.example.com) — 2026-10-05T21:41:56+00:00

2026/08/12 18:45		current
Line 15:		Line 15:
	* Deprecate <php>is_a</php> with $object_or_class not being a string or object		* Deprecate <php>is_a</php> with $object_or_class not being a string or object
	* Deprecate <php>is_subclass_of</php> with $object_or_class not being a string or object		* Deprecate <php>is_subclass_of</php> with $object_or_class not being a string or object
		+	* Deprecate the b prefix for binary strings

	===== Proposals =====		===== Proposals =====
Line 57:		Line 58:
	</blockquote>		</blockquote>

		+	==== Deprecate the b prefix for binary strings ====
		+
		+	* Author: Daniel Scherzer <daniel.e.scherzer@gmail.com>
		+	* Juliette Reinders Folmer <php-internals_nospam@adviesenzo.nl>
		+
		+	TODO https://news-web.php.net/php.internals/132634

io_terminal - Update to v0.4: concrete Terminal and ModeToken classes, ordinary-stream input, explicit raw-mode restoration, and clarified input and mode contracts.

prateekbhujel (prateekbhujel@undisclosed.example.com) — 2026-10-05T20:37:26+00:00

2026/10/05 20:37		current
Line 415:		Line 415:
	Reference extension: https://github.com/prateekbhujel/php-terminal		Reference extension: https://github.com/prateekbhujel/php-terminal

-	The candidate includes PHPTs for creation, sizing, scripted-stream input, raw-mode leases, key decoding, timeouts, resize handling, UTF-8 fragments, line input, buffered and redirected streams, and secret input.	+	The implementation includes PHPTs for creation, sizing, scripted-stream input, raw-mode leases, key decoding, timeouts, resize handling, UTF-8 fragments, line input, buffered and redirected streams, and secret input.

	POSIX PTY tests cover multiple wrappers for one terminal, unrelated terminals, out-of-order lease release, cross-wrapper restoration, token lifetime, EOF, restoration after closing the original stream, and line reads from nonblocking terminal descriptors. Additional tests cover output-mode preservation, fork ownership, and acquisition/restoration failures.		POSIX PTY tests cover multiple wrappers for one terminal, unrelated terminals, out-of-order lease release, cross-wrapper restoration, token lifetime, EOF, restoration after closing the original stream, and line reads from nonblocking terminal descriptors. Additional tests cover output-mode preservation, fork ownership, and acquisition/restoration failures.

-	Native Windows console scenarios have been run locally in a Windows 11 ARM64 VM using a console harness that injects native input records. These exercise the console path, including Unicode, repeat counts, key decoding, secret input, line input, and restoration. Ordinary-stream tests exercise the separate byte-stream path and are not substitutes for native console tests.	+	Input-transition regressions cover retained UTF-8 bytes and CRLF handling across secret, key, and line reads, including split delimiters and preservation of line data. Timeout tests cover nonblocking reads and overall deadlines during input and escape-sequence processing.

-	The local official Windows ''run-tests.php'' execution remains unresolved. Results from a supplemental runner and the native harness do not establish that the official Windows PHPT suite passes; official Windows CI confirmation remains pending.	+	Native Windows console checks use a separate harness that injects console input records to exercise key decoding, Unicode, repeat counts, secret input, line input, and mode restoration. Ordinary-stream tests exercise the byte-stream path and do not replace native console checks.

-	The candidate includes fixes and focused regressions for CRLF normalization when line input follows a CR-terminated secret, and enforcement of the overall positive secret deadline during escape-sequence processing. The CRLF regression passed through the official PHPT runner on macOS and a supplemental runner on Windows 11 ARM64, including preservation of a data CR before CRLF and a bare CR at EOF. Focused positive-deadline and zero-timeout checks also passed locally on both platforms. These results do not establish completion of the official Windows PHPT suite.	+	Current build and test results are available in the implementation PR.

	===== Implementation =====		===== Implementation =====

bcrypt_sha256

sjoerd (sjoerd@undisclosed.example.com) — 2026-10-05T13:13:59+00:00

2026/10/05 09:09		current
Line 3:		Line 3:
	* Date: 2026-10-04		* Date: 2026-10-04
	* Author: Sjoerd Langkemper, sjoerd-php@linuxonly.nl		* Author: Sjoerd Langkemper, sjoerd-php@linuxonly.nl
-	* Status: Draft	+	* Status: Under discussion
	* Implementation: https://github.com/php/php-src/pull/24073		* Implementation: https://github.com/php/php-src/pull/24073
-	* Discussion thread: tbd	+	* Discussion thread: https://news-web.php.net/php.internals/132784
	* Voting thread: tbd		* Voting thread: tbd

rfc - opened vote for "End PEAR Project Endorsement"

nicksdot (nicksdot@undisclosed.example.com) — 2026-10-05T13:12:24+00:00

2026/10/05 09:21		current
Line 13:		Line 13:
	This section is for RFCs that are currently being voted on.		This section is for RFCs that are currently being voted on.

-	* None	+	* [[rfc:end_pear_endorsement\|End PEAR Project Endorsement]] (Created 2026-08-27)

	===== Under Discussion =====		===== Under Discussion =====
Line 27:		Line 27:
	* [[rfc:reldateformatter\|IntlRelativeDateTimeFormatter]] (Created 2026-08-07, Discussion started 2026-08-07)		* [[rfc:reldateformatter\|IntlRelativeDateTimeFormatter]] (Created 2026-08-07, Discussion started 2026-08-07)
	* [[rfc:preg_throw_on_error\|PREG_THROW_ON_ERROR]] (Created 2026-07-28, Discussion started 2026-07-28)		* [[rfc:preg_throw_on_error\|PREG_THROW_ON_ERROR]] (Created 2026-07-28, Discussion started 2026-07-28)
-	* [[rfc:end_pear_endorsement\|End PEAR Project Endorsement]] (Created 2026-08-27)
	* [[rfc:throw_error_for_invalid_characters_for_number_base\|Throw ValueError for invalid characters in number base functions]] (Created 2026-08-11)		* [[rfc:throw_error_for_invalid_characters_for_number_base\|Throw ValueError for invalid characters in number base functions]] (Created 2026-08-11)
	* [[rfc:function-autoloading-five-oh\|Function Autoloading (mark 5)]] (created 2026-06-16, discussion started 2026-06-16, voting started 2026-07-30)		* [[rfc:function-autoloading-five-oh\|Function Autoloading (mark 5)]] (created 2026-06-16, discussion started 2026-06-16, voting started 2026-07-30)

end_pear_endorsement - opened vote

nicksdot (nicksdot@undisclosed.example.com) — 2026-10-05T13:11:11+00:00

2026/10/05 13:11		current
Line 67:		Line 67:
	title="Stop endorsing PEAR?"		title="Stop endorsing PEAR?"
	voteType="single"		voteType="single"
-	closed="true"	+	closed="false"
	closeon="2026-10-19T13:15:00Z"		closeon="2026-10-19T13:15:00Z"
	>		>

query_params

kocsismate (kocsismate@undisclosed.example.com) — 2026-10-04T20:39:43+00:00

bcrypt_max_password_length

sjoerd (sjoerd@undisclosed.example.com) — 2026-10-04T10:00:44+00:00

2026/10/04 09:48		current
Line 92:		Line 92:
	==== To SAPIs ====		==== To SAPIs ====
	None.		None.
		+
		+	===== Discussion =====
		+
		+	Opposition arguments:
		+
		+	* Backward compatibility is a major concern: users with existing long passwords could suddenly face exceptions, breaking previously working logins. Introducing a ValueError risks crashing applications for users who happen to submit long passwords.
		+	* The limit is 72 bytes, not characters, so non-ASCII users (especially those using multi-byte scripts) would be disproportionately affected.
		+	* 72 bytes already provides enough entropy for strong passphrases (e.g., 8-word Diceware), so rejecting longer input is seen as a usability cost without a real security gain.
		+	* Truncation is simply documented, correct algorithm behavior, not "corruption" of input.
		+	* Rehashing during login (via ''password_needs_rehash()'') could still surface the error for existing users with long passwords when algorithm parameters change.
		+
		+	Support arguments:
		+
		+	* Silent truncation already causes real harm, such as false-positive logins and broken "password must differ from previous" checks; a noisy failure is preferable because it prompts developers to fix the underlying issue.
		+	* NIST guidance explicitly advises against truncating passwords, and real-world incidents (including at major companies) show truncation behavior has contributed to security issues.
		+	* An API that silently accepts and mishandles long input is a poor design; developers deserve a clear signal rather than a hidden security gap.

	===== Open Issues =====		===== Open Issues =====
		+
	None at present.		None at present.

array_shorthand - version 1.4

weilindu (weilindu@undisclosed.example.com) — 2026-10-03T07:44:07+00:00

2026/10/01 07:08		current
Line 1:		Line 1:
	====== PHP RFC: Array Variable Shorthand ======		====== PHP RFC: Array Variable Shorthand ======

-	* Version: 1.2	+	* Version: 1.4
-	* Date: 2026-09-30	+	* Date: 2026-10-03
	* Author: Weilin Du, weilindu@php.net		* Author: Weilin Du, weilindu@php.net
	* Status: Under Discussion		* Status: Under Discussion
Line 11:		Line 11:
	===== Introduction =====		===== Introduction =====

-	Associative arrays often repeat a key and a variable with the same name. This RFC proposes ''=$name'' as shorthand for ''"name" => $name'' in array construction and destructuring:	+	Associative arrays often repeat a key and a variable with the same name. This RFC proposes '':$name'' as shorthand for ''"name" => $name'' in array construction and destructuring:

	<PHP>		<PHP>
Line 18:		Line 18:
	$y = 20;		$y = 20;

-	$point = [=$x, =$y]; // $point = ['x' => $x, 'y' => $y]	+	$point = [:$x, :$y]; // $point = ['x' => $x, 'y' => $y]
-	[=$x, =$y] = $point; // ['x' => $x, 'y' => $y] = $point	+	[:$x, :$y] = $point; // ['x' => $x, 'y' => $y] = $point
-	$point = array(=$x, =$y); // array('x' => $x, 'y' => $y)	+	$point = array(:$x, :$y); // array('x' => $x, 'y' => $y)
-	list(=$x, =$y) = $point; // list('x' => $x, 'y' => $y) = $point	+	list(:$x, :$y) = $point; // list('x' => $x, 'y' => $y) = $point
	?>		?>
	</PHP>		</PHP>
Line 27:		Line 27:
	===== Proposal =====		===== Proposal =====

-	An array element written ''=$name'' is equivalent to ''"name" => $name''. The key is the exact, case-sensitive variable name without the leading ''$''. This applies to both array constructors (''[]'' and ''array()'') and destructuring patterns (''[]'' and ''list()''). In construction, the variable is read; in destructuring, the value at that key is assigned to the variable. All existing behavior of an explicit keyed element applies, including duplicate keys and missing-key warnings.	+	An array element written '':$name'' is equivalent to ''"name" => $name''. The key is the exact, case-sensitive variable name without the leading ''$''. This applies to both array constructors (''[]'' and ''array()'') and destructuring patterns (''[]'' and ''list()''). In construction, the variable is read; in destructuring, the value at that key is assigned to the variable. All existing behavior of an explicit keyed element applies, including duplicate keys and missing-key warnings.

-	Here, ''$name'' means one directly named variable token (''T_VARIABLE''). The shorthand does not accept variable variables, array dimensions, object or static properties, or arbitrary expressions: ''=$$name'', ''=$name[0]'', and ''=$object->name'' are invalid. For those values, write an explicit key, for example ''["name" => $object->name]''.	+	Here, ''$name'' means one directly named variable token (''T_VARIABLE''). The shorthand does not accept variable variables, array dimensions, object or static properties, or arbitrary expressions: '':$$name'', '':$name[0]'', and '':$object->name'' are invalid. For those values, write an explicit key, for example ''["name" => $object->name]''.

-	Whitespace between ''='' and the variable is allowed.	+	Whitespace after '':'' is allowed. This includes an ASCII space, tab (''\t''), line feed (''\n''), and carriage return (''\r''). Comments may also appear between '':'' and the variable.

-	The identifier determines the variable and its corresponding case-sensitively.	+	The identifier determines both the variable and its string key preserving case exactly.

-	The shorthand works at any nesting level and in destructuring patterns used by ''foreach''. It adds an array-element form but not a function-argument form. ''foo(=$name)'' is invalid. ''array()'' and ''list()'' are language constructs with array-element syntax, so they are included alongside their ''[]'' equivalents.	+	The shorthand works at any nesting level and in destructuring patterns used by ''foreach''. It adds an array-element form but not a function-argument form. ''foo(:$name)'' is invalid. ''array()'' and ''list()'' are language constructs with array-element syntax, so they are included alongside their ''[]'' equivalents.
-		+
-	==== Why ''='' instead of '':''? ====	+
-		+
-	An earlier draft used '':$name''. But '':'' is already part of PHP's ternary expression, and ''[$condition ? 'bar' :$baz]'' is valid array syntax. Giving '':'' a second role inside array elements would require the parser and readers to distinguish this ternary colon from the shorthand prefix. The proposed ''=$name'' avoids that.	+

	==== Examples ====		==== Examples ====
Line 51:		Line 47:
	$name = 'Weilin';		$name = 'Weilin';
	$age = 26;		$age = 26;
-	$user = ['id' => 1, =$name, =$age];	+	$user = ['id' => 1, :$name, :$age];
	// ['id' => 1, 'name' => 'Weilin', 'age' => 26]		// ['id' => 1, 'name' => 'Weilin', 'age' => 26]
	?>		?>
Line 62:		Line 58:
	$name = 'Weilin';		$name = 'Weilin';
	$values = [10, 20];		$values = [10, 20];
-	$result = [...$values, =$name,];	+	$result = [...$values, :$name,];
	// [0 => 10, 1 => 20, 'name' => 'Weilin']		// [0 => 10, 1 => 20, 'name' => 'Weilin']
	?>		?>
Line 74:		Line 70:
	<?php		<?php
	$user = ['name' => 'Weilin', 'age' => 26];		$user = ['name' => 'Weilin', 'age' => 26];
-	[=$name, 'age' => $years] = $user;	+	[:$name, 'age' => $years] = $user;
	// $name === 'Weilin'; $years === 26		// $name === 'Weilin'; $years === 26
	?>		?>
Line 84:		Line 80:
	<?php		<?php
	$user = ['name' => 'Weilin', 'age' => 26];		$user = ['name' => 'Weilin', 'age' => 26];
-	list(=$name, 'age' => $years) = $user;	+	list(:$name, 'age' => $years) = $user;
	// $name === 'Weilin'; $years === 26		// $name === 'Weilin'; $years === 26
		+	?>
		+	</PHP>
		+
		+	=== ArrayAccess destructuring ===
		+
		+	An object implementing ''ArrayAccess'' can be destructured by key, as with an explicit keyed element. This reads an array offset, not an object property:
		+
		+	<PHP>
		+	<?php
		+	$object = new ArrayObject(['name' => 'Ada']);
		+	[:$name] = $object; // Equivalent to ['name' => $name] = $object
		+	echo $name; // Ada
		+	list(:$name) = $object;
		+	echo $name; // Ada
	?>		?>
	</PHP>		</PHP>
Line 96:		Line 106:
	<?php		<?php
	$rows = [['name' => 'Weilin']];		$rows = [['name' => 'Weilin']];
-	foreach ($rows as [=$name]) {	+	foreach ($rows as [:$name]) {
	echo $name; // Weilin		echo $name; // Weilin
	}		}
Line 109:		Line 119:
	<?php		<?php
	$name = 'Weilin';		$name = 'Weilin';
-	$user = array('id' => 1, =$name); // array('id' => 1, 'name' => 'Weilin')	+	$user = array('id' => 1, :$name); // array('id' => 1, 'name' => 'Weilin')
-	list(=$name) = $user; // $name === 'Weilin'	+	list(:$name) = $user; // $name === 'Weilin'
-	foreach (array($user) as list(=$name)) {	+	foreach (array($user) as list(:$name)) {
	echo $name; // Weilin		echo $name; // Weilin
	}		}
Line 124:		Line 134:
	<?php		<?php
	$name = 'Weilin';		$name = 'Weilin';
-	$record = ['user' => array(=$name)];	+	$record = ['user' => array(:$name)];
	// ['user' => ['name' => 'Weilin']]		// ['user' => ['name' => 'Weilin']]
-	list('user' => [=$name]) = $record;	+	['user' => [:$name]] = $record;
	echo $name; // Weilin		echo $name; // Weilin
	?>		?>
Line 136:		Line 146:
	<?php		<?php
	$record = ['user' => ['name' => 'Ada']];		$record = ['user' => ['name' => 'Ada']];
-	list('user' => list(=$name)) = $record;	+	list('user' => list(:$name)) = $record;
	echo $name; // Ada		echo $name; // Ada
		+	?>
		+	</PHP>
		+
		+	You cannot mix ''[]'' with ''list()'' within one nested destructuring pattern. This is an existing restriction, including when no shorthand is used:
		+
		+	<PHP>
		+	<?php
		+	$record = ['user' => ['name' => 'Ada']];
		+	['user' => [:$name]] = $record; // Valid
		+	list('user' => list(:$name)) = $record; // Valid
		+	list('user' => [:$name]) = $record; // Invalid: cannot mix list() and []
		+	?>
		+	</PHP>
		+
		+	=== Keyed and unkeyed destructuring ===
		+
		+	You cannot mix keyed and unkeyed elements at the same level of a destructuring pattern. This also applies without the shorthand. Array construction can still mix them:
		+
		+	<PHP>
		+	<?php
		+	$name = 'Weilin';
		+	$age = 26;
		+	$user = [$age, :$name]; // Valid construction: [0 => 26, 'name' => 'Weilin']
		+	[:$name, $age] = $user; // Invalid: keyed and unkeyed at the same level
	?>		?>
	</PHP>		</PHP>
Line 146:		Line 180:
	<?php		<?php
	$name = 'new';		$name = 'new';
-	$first = ['name' => 'old', =$name]; // ['name' => 'new']	+	$first = ['name' => 'old', :$name]; // ['name' => 'new']
-	$second = [=$name, 'name' => 'later']; // ['name' => 'later']	+	$second = [:$name, 'name' => 'later']; // ['name' => 'later']
		+	?>
		+	</PHP>
		+
		+	=== Unpacking with duplicate keys ===
		+
		+	When array unpacking and the shorthand produce the same string key, the later element wins:
		+
		+	<PHP>
		+	<?php
		+	$name = 'new';
		+	$first = [...['name' => 'old'], :$name]; // ['name' => 'new']
		+	$second = [:$name, ...['name' => 'later']]; // ['name' => 'later']
	?>		?>
	</PHP>		</PHP>
Line 155:		Line 201:
	<PHP>		<PHP>
	<?php		<?php
-	[=$name] = []; // Warning: Undefined array key "name"	+	[:$name] = []; // Warning: Undefined array key "name"
	var_dump($name); // NULL		var_dump($name); // NULL
	?>		?>
Line 166:		Line 212:
	<PHP>		<PHP>
	<?php		<?php
-	[=$$name]; // Invalid: variable variable	+	[:$$name]; // Invalid: variable variable
-	[=$name[0]]; // Invalid: array dimension	+	[:$name[0]]; // Invalid: array dimension
-	[=$object->name]; // Invalid: object property	+	[:$object->name]; // Invalid: object property
-	[=$class::$property]; // Invalid: static property	+	[:$class::$property]; // Invalid: static property
-	[=($name)]; // Invalid: expression	+	[:($name)]; // Invalid: expression
	['name' => $object->name]; // Valid		['name' => $object->name]; // Valid
	?>		?>
Line 181:		Line 227:
	$Name = 'upper';		$Name = 'upper';
	$name = 'lower';		$name = 'lower';
-	echo json_encode([= $Name, =$name]); // {"Name":"upper","name":"lower"}	+	echo json_encode([: $Name, :$name]); // {"Name":"upper","name":"lower"}
		+	*$array = [: / key from the variable name / $name]; // ['name' => 'lower']*
	?>		?>
	</PHP>		</PHP>
Line 191:		Line 238:
	<PHP>		<PHP>
	<?php		<?php
-	$array = [=$missing]; // Warning: Undefined variable $missing	+	$array = [:$missing]; // Warning: Undefined variable $missing
	// ['missing' => null]		// ['missing' => null]
	?>		?>
Line 198:		Line 245:
	=== References ===		=== References ===

-	The shorthand reads the variable by value. A reference requires the existing explicit-key form:	+	When constructing an array, ''[:$name]'' does not create a new reference to the original variable. A reference requires the existing explicit-key form:

	<PHP>		<PHP>
	<?php		<?php
	$name = 'before';		$name = 'before';
-	$byValue = [=$name];	+	$byValue = [:$name];
	$byReference = ['name' => &$name];		$byReference = ['name' => &$name];
	$name = 'after';		$name = 'after';
	echo $byValue['name']; // before		echo $byValue['name']; // before
	echo $byReference['name']; // after		echo $byReference['name']; // after
-	// [=&$name] is invalid.	+	// [:&$name] is invalid.
		+	?>
		+	</PHP>
		+
		+	When destructuring, assignment to ''$name'' follows ordinary assignment. If ''$name'' is already a reference, the value it points to is overwritten:
		+
		+	<PHP>
		+	<?php
		+	$target = 'before';
		+	$name =& $target;
		+
		+	[:$name] = ['name' => 'after'];
		+	echo $target; // after
	?>		?>
	</PHP>		</PHP>
Line 248:		Line 307:
	===== Patches and Tests =====		===== Patches and Tests =====

-	TBD	+	The draft implementation and PHPT tests are available at [[https://github.com/php/php-src/pull/24034\|php-src PR #24034]].

	===== Implementation =====		===== Implementation =====

-	TBD. The implementation will be added soon.	+	See [[https://github.com/php/php-src/pull/24034\|draft implementation in php-src PR #24034]].

	===== References =====		===== References =====
Line 258:		Line 317:
	* [[https://wiki.php.net/rfc/named_params#shorthand_syntax_for_matching_parameter_and_variable_name\|Named Arguments RFC: Future Scope]]		* [[https://wiki.php.net/rfc/named_params#shorthand_syntax_for_matching_parameter_and_variable_name\|Named Arguments RFC: Future Scope]]
	* [[https://www.php.net/manual/en/language.types.array.php#language.types.array.destructuring\|PHP manual: array destructuring]]		* [[https://www.php.net/manual/en/language.types.array.php#language.types.array.destructuring\|PHP manual: array destructuring]]
		+	* [[https://www.php.net/manual/en/class.arrayaccess.php\|PHP manual: ArrayAccess]]
		+	* [[https://www.php.net/manual/en/language.types.array.php#language.types.array.unpacking\|PHP manual: array unpacking]]
		+	* [[https://github.com/php/php-src/blob/179753061cb2268132310748fa8556b90cc4d52f/Zend/zend_language_scanner.l#L1409\|PHP source: lexical whitespace definition]]
		+	* [[https://docs.raku.org/syntax/Colon%20Pair\|Raku documentation: colon pairs]]
		+	* [[https://perldoc.perl.org/perlop#Comma-Operator\|Perl documentation: the fat comma]]
		+	* [[https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Object_initializer#property_definitions\|MDN: JavaScript shorthand properties]]
		+	* [[https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Destructuring\|MDN: JavaScript object destructuring]]

	===== Rejected Features =====		===== Rejected Features =====

-	The '':$name'' spelling was rejected because of its overlap with ternary syntax inside arrays.	+	An earlier equals-sign prefix was replaced with '':$name''.

	===== Changelog =====		===== Changelog =====
Line 268:		Line 334:
	* 2026-09-30: Added examples and changed status to Under Discussion.		* 2026-09-30: Added examples and changed status to Under Discussion.
	* 2026-09-30: Included ''array()'' and ''list()'' and specified which variables qualify.		* 2026-09-30: Included ''array()'' and ''list()'' and specified which variables qualify.
-	* 2026-09-30: Changed the spelling to ''=$name'' and documented the ternary-syntax overlap.	+	* 2026-09-30: Documented the ternary-syntax overlap.
		+	* 2026-10-03: Changed the shorthand spelling to '':$name'' and added ArrayAccess and unpacking examples.
		+	* 2026-10-03: Documented Raku and JavaScript shorthand as prior art.
		+	* 2026-10-03: Clarified whitespace, ternary parsing, nested destructuring, keyed/unkeyed elements, references, and implementation status.

invalid_filter_options

arshidkv12 (arshidkv12@undisclosed.example.com) — 2026-10-03T05:37:31+00:00

2026/10/03 05:33		current
Line 1:		Line 1:
-	====== PHP RFC: Deprecate Invalid Filter Options and Throw ValueError ======	+	====== PHP RFC: Deprecate Invalid Filter Options ======
	* Version: 0.9		* Version: 0.9
	* Date: 2026-10-03		* Date: 2026-10-03

poll_api_additions

bukka (bukka@undisclosed.example.com) — 2026-10-01T13:52:38+00:00

2026/09/30 17:42		current
Line 753:		Line 753:
	===== Patches and Tests =====		===== Patches and Tests =====

-	A working implementation is part of the ''io_hooks_poc'' branch at	+	A working implementation is part of the IO hooks pull request at https://github.com/php/php-src/pull/23997, in
-	https://github.com/bukka/php-src/tree/io_hooks_poc, in ''main/poll'' and ''ext/standard/io_poll*'', with tests	+	''main/poll'' and ''ext/standard/io_poll*'', with tests in ''ext/standard/tests/poll'' and
-	in ''ext/standard/tests/poll'' and ''ext/sockets/tests''. It will be extracted into a pull request of its own.	+	''ext/sockets/tests''. It will be extracted into a pull request of its own.

	===== Implementation =====		===== Implementation =====
Line 766:		Line 766:

	* [[rfc:poll_api\|PHP RFC: Polling API]]		* [[rfc:poll_api\|PHP RFC: Polling API]]
		+	* Design document covering this RFC, the IO hooks and the Ring: https://gist.github.com/bukka/87359261a4bfaa572ce43c93c0554b55
	* signalfd: https://man7.org/linux/man-pages/man2/signalfd.2.html		* signalfd: https://man7.org/linux/man-pages/man2/signalfd.2.html
	* pidfd_open: https://man7.org/linux/man-pages/man2/pidfd_open.2.html		* pidfd_open: https://man7.org/linux/man-pages/man2/pidfd_open.2.html

io_hooks

bukka (bukka@undisclosed.example.com) — 2026-10-01T13:52:25+00:00

2026/09/30 17:49		current
Line 969:		Line 969:
	===== Patches and Tests =====		===== Patches and Tests =====

-	A working implementation is on the ''io_hooks_poc'' branch at	+	A working implementation is in the pull request at https://github.com/php/php-src/pull/23997. The tests are in
-	https://github.com/bukka/php-src/tree/io_hooks_poc. The tests are in ''ext/standard/tests/streams/hooks'',	+	''ext/standard/tests/streams/hooks'', ''ext/curl/tests'', ''ext/openssl/tests'' and ''ext/sockets/tests''. The
-	''ext/curl/tests'', ''ext/openssl/tests'' and ''ext/sockets/tests''. The branch also contains the Ring, so the	+	branch also contains the Ring, so the API was designed and tested against a readiness and a completion
-	API was designed and tested against a readiness and a completion executor at once and is known to accommodate	+	executor at once and is known to accommodate the Ring. The provider the tests use is the scheduler shown
-	the Ring. The provider the tests use is the scheduler shown above, in ''scheduler.inc'', and	+	above, in ''scheduler.inc'', and ''context-provider.inc'' is a provider on a bare ''Io\Poll\Context'' without
-	''context-provider.inc'' is a provider on a bare ''Io\Poll\Context'' without a queue. The tests in	+	a queue. The tests in ext/standard cover the operations, registrations, cancellation, frozen streams,
-	ext/standard cover the operations, registrations, cancellation, frozen streams, processes, signals, sleeping	+	processes, signals, sleeping and request shutdown, and the extension tests cover ''curl_exec()'' and
-	and request shutdown, and the extension tests cover ''curl_exec()'' and ''curl_multi_select()'', TLS streams	+	''curl_multi_select()'', TLS streams and ext/sockets.
-	and ext/sockets.	+

	===== Implementation =====		===== Implementation =====
Line 989:		Line 988:
	* [[rfc:poll_api\|PHP RFC: Polling API]]		* [[rfc:poll_api\|PHP RFC: Polling API]]
	* [[rfc:poll_api_additions\|PHP RFC: Polling API additions]]		* [[rfc:poll_api_additions\|PHP RFC: Polling API additions]]
		+	* Design document covering the Polling API additions, this RFC and the Ring: https://gist.github.com/bukka/87359261a4bfaa572ce43c93c0554b55
	* Async core RFC: https://github.com/true-async/php-async-core-rfc		* Async core RFC: https://github.com/true-async/php-async-core-rfc
	* Go's network poller: https://go.dev/src/runtime/netpoll.go		* Go's network poller: https://go.dev/src/runtime/netpoll.go

io_ring

bukka (bukka@undisclosed.example.com) — 2026-10-01T13:52:04+00:00

2026/09/30 17:50		current
Line 459:		Line 459:
	===== Backward Incompatible Changes =====		===== Backward Incompatible Changes =====

-	None. The RFC adds the ''Io\Ring'' namespace and the ''accept_multishot'' stream context option, which is read	+	None.
-	only under a provider with ''DirectAccept''. Bundling ior adds a library to the PHP build, as pcre2 and others	+
-	are.	+

	===== Proposed PHP Version(s) =====		===== Proposed PHP Version(s) =====
Line 522:		Line 520:
	===== Patches and Tests =====		===== Patches and Tests =====

-	A working implementation is on the ''io_hooks_poc'' branch at	+	A working implementation is in the IO hooks pull request at https://github.com/php/php-src/pull/23997. The
-	https://github.com/bukka/php-src/tree/io_hooks_poc. The hooks test suite in	+	hooks test suite in ''ext/standard/tests/streams/hooks'' runs every scenario on the Ring as well, on both
-	''ext/standard/tests/streams/hooks'' runs every scenario on the Ring as well, on both Linux backends, and CI	+	Linux backends, and CI runs the hooks, poll, TLS and curl tests on the Ring on Linux, macOS and Windows. ior
-	runs the hooks, poll, TLS and curl tests on the Ring on Linux, macOS and Windows. ior is at	+	is at https://github.com/libior/ior.
-	https://github.com/libior/ior.	+

	===== Implementation =====		===== Implementation =====
Line 538:		Line 535:
	* [[rfc:io_hooks\|PHP RFC: IO hooks and operations]]		* [[rfc:io_hooks\|PHP RFC: IO hooks and operations]]
	* [[rfc:poll_api_additions\|PHP RFC: Polling API additions]]		* [[rfc:poll_api_additions\|PHP RFC: Polling API additions]]
		+	* Design document covering the Polling API additions, the IO hooks and this RFC: https://gist.github.com/bukka/87359261a4bfaa572ce43c93c0554b55
	* ior: https://github.com/libior/ior		* ior: https://github.com/libior/ior
	* io_uring: https://kernel.dk/io_uring.pdf		* io_uring: https://kernel.dk/io_uring.pdf

time_instant_class - Explicitly mention that Instant is immutable at the start of the proposal.

timwolla (timwolla@undisclosed.example.com) — 2026-09-30T18:11:21+00:00

2026/09/29 17:00		current
Line 34:		Line 34:
	===== Proposal =====		===== Proposal =====

-	Add a new always-available class <php>Time\Instant</php> representing a “point in time” together with an interface <php>Time\Clock</php> and a <php>Time\Clock\SystemClock</php> implementation.	+	Add a new always-available, immutable, class <php>Time\Instant</php> representing a “point in time” together with an interface <php>Time\Clock</php> and a <php>Time\Clock\SystemClock</php> implementation.

	<PHP>		<PHP>

pdo_binary

calvinb (calvinb@undisclosed.example.com) — 2026-09-30T17:57:33+00:00

2026/09/30 17:57		current
Line 62:		Line 62:
	=== Emulated prepares ===		=== Emulated prepares ===

-	If binary values requires special handling as literal values in queries, then quoters will have to convert binary parameters. For example, SQL Server requires hex-encoding binary data that can't be put into a normal string such as nul bytes.	+	If binary values require special handling as literal values in queries, then quoters will have to convert binary parameters. For example, SQL Server requires hex-encoding binary data that can't be put into a normal string such as null bytes.

	=== Attributes ===		=== Attributes ===

surface3d.png - created

pajoye (pajoye@undisclosed.example.com) — 2026-07-19T13:48:10+00:00

	current

scaled_on_load_rotate.png - created

pajoye (pajoye@undisclosed.example.com) — 2026-07-17T06:47:24+00:00

	current

watermarked.png - created

pajoye (pajoye@undisclosed.example.com) — 2026-07-17T03:57:25+00:00

	current

scale_entropy_visual_check.png - created

pajoye (pajoye@undisclosed.example.com) — 2026-07-14T03:12:03+00:00

	current

textcurve.png - created

pajoye (pajoye@undisclosed.example.com) — 2026-07-10T14:08:53+00:00

1783692513	current

gradient_art.png - created

pajoye (pajoye@undisclosed.example.com) — 2026-07-06T06:32:24+00:00

	current

2026/10/04 20:32		current
Line 376:		Line 376:
	This behavior deviates from the percent-encoding rules of the query component of WHATWG URL, as the [[https://url.spec.whatwg.org/#query-percent-encode-set\|query percent-encode set]] contains far fewer characters, and the space code point is handled differently again.		This behavior deviates from the percent-encoding rules of the query component of WHATWG URL, as the [[https://url.spec.whatwg.org/#query-percent-encode-set\|query percent-encode set]] contains far fewer characters, and the space code point is handled differently again.

-	It's also important to compare how the percent encoding rules of RFC 1866's as well as WHATWG URL's application/x-www-form-urlencoded media type differ: RFC 1866 doesn't percent-encode the asterisk ('''') symbol, but* WHATWG URL does so.	+	It's also important to compare how the percent encoding rules of RFC 1866's as well as WHATWG URL's application/x-www-form-urlencoded media type differ: RFC 1866 percent-encodes the asterisk ('''') symbol as ''%2A'', while* WHATWG URL leaves it unescaped.

	=== Recomposition ===		=== Recomposition ===
Line 652:		Line 652:

	* Empty array: An array containing no elements.		* Empty array: An array containing no elements.
-	* List:**** * List: An array whose keys are consecutive integers starting from ''0'', in iteration order, as determined by ''array_is_list()''.	+	* List: An array whose keys are consecutive integers starting from ''0'', in iteration order, as determined by ''array_is_list()''.
	* Map: A non-empty array is a map if it is not a list.		* Map: A non-empty array is a map if it is not a list.

Line 660:		Line 660:
	* Non-array values are converted according to the rules described in the "Supported types" section, using the present building options.		* Non-array values are converted according to the rules described in the "Supported types" section, using the present building options.
	* Empty arrays are omitted, since they contain no items which could be added to the query parameter list.		* Empty arrays are omitted, since they contain no items which could be added to the query parameter list.
-	* For a nested list containing no array elements, ''[]'' is appended to the resulting query parameter name for each element. For example, the ''["k" => [1, 2]]'' input is internally stored as two parameters: ''[["k[]" => "1"], ["k[]" => "2"]]''.	+	* For a nested list containing no array elements, ''[]'' is appended to the resulting query parameter name for each element. For example, the ''["k" => [1, 2]]'' input is internally stored as two parameters: ''%%[["k[]" => "1"], ["k[]" => "2"]]%%''.
-	* If a nested list contains at least one array element, the original numeric index is included for every element at that level. For example, the ''["k" => [1, ["a" => 2]]]'' input is internally stored as ''[["k[0]" => "1"], ["k[1][a]" => "2"]]''.	+	* If a nested list contains at least one array element, the original numeric index is included for every element at that level. For example, the ''["k" => [1, ["a" => 2]]]'' input is internally stored as ''%%[["k[0]" => "1"], ["k[1][a]" => "2"]]%%''.
-	* For a nested map, each key is appended to the parameter name within brackets. For example, the ''["k" => ["a" => 1, "b" => 2]]'' input is internally stored as ''[["k[a]" => "1"], ["k[b]" => "2"]]''.	+	* For a nested map, each key is appended to the parameter name within brackets. For example, the ''["k" => ["a" => 1, "b" => 2]]'' input is internally stored as ''%%[["k[a]" => "1"], ["k[b]" => "2"]]%%''.
	* These rules apply recursively.		* These rules apply recursively.