Re: [PHP-DEV] [RFC] [VOTE] Deprecate type juggling to and from bool type within the function type juggling context

Hey, On 21.7.2025 14:21:49, Gina P. Banyard wrote: Hello internals, I have started the vote for my "Deprecate type juggling to and from bool type within the function type juggling context" RFC: https://wiki.php.net/rfc/deprecate-function-bool-type-juggling It will run for two weeks and close

Re: [PHP-DEV] Study on unsafe extract() usage

 Hey Kamil, On 23.7.2025 21:01:14, Kamil Tekiela wrote: This would prevent most of the vulnerabilities found in the dataset and we cannot think of a valid use case for allowing this behavior But not all. This function is dangerous on its own. Attack vectors are 99% throug

Re: [PHP-DEV] [RFC] Deprecations for PHP 8.5

Hey Tim, On 6.7.2025 15:35:16, Tim Düsterhus wrote: Hi Since this is a recurring thing, I feel compelled to point out terminology: A deprecation in itself is not a breaking change. Let me disagree with this. Yes, a deprecation in *itself* doesn't break running code. However it is both a) an

Re: [PHP-DEV] [RFC] Deprecations for PHP 8.5

Hey, On 4.7.2025 09:01:52, Niels Dossche wrote: Hi First of all, that's a huge list of deprecations and I think we should tone down on that. Especially if a feature still has a purpose and is not harmful or buggy, then we should probably consider not deprecating it. Yeah, I agree. The list

Re: [PHP-DEV] [RFC] Transform void into an alias for null

On 5.6.2025 02:59:56, Daniel Scherzer wrote: On Wed, Jun 4, 2025 at 4:49 PM Bob Weinand wrote: Hey Daniel, where's the BC break? Nothing which worked today will stop working (except you won't get exceptions in some cases). That's not a BC break. The only th

Re: [PHP-DEV] [RFC] Transform void into an alias for null

On 4.6.2025 22:39:28, Daniel Scherzer wrote: On Wed, Jun 4, 2025 at 1:35 PM Bob Weinand wrote: On 4.6.2025 16:54:05, Bob Weinand wrote: > On 2.6.2025 18:27:51, Gina P. Banyard wrote: >> Hello internals, >> >> This is the second RFC out of a set of typ

Re: [PHP-DEV] [RFC] Transform void into an alias for null

On 2.6.2025 18:27:51, Gina P. Banyard wrote: Hello internals, This is the second RFC out of a set of type system related RFCs I want to propose for PHP 8.5. The objective is to fix a weird quirk of PHP's type system, where void lives in its own type hierarchy. This is visible mainly in that a

Re: [PHP-DEV][RFC] Deprecate type juggling to and from bool type within the function type juggling context

On 4.6.2025 18:46:58, Larry Garfield wrote: On Wed, Jun 4, 2025, at 11:16 AM, Theodore Brown wrote: On Wed, June 4, 2025 at 09:37 Aleksander Machniak wrote: On 4.06.2025 16:03, G. P. Banyard wrote: I don't understand what you mean. The purpose is to deprecate the behaviour in 8.5 so that it c

Re: [PHP-DEV] [RFC] Transform void into an alias for null

On 4.6.2025 16:54:05, Bob Weinand wrote: On 2.6.2025 18:27:51, Gina P. Banyard wrote: Hello internals, This is the second RFC out of a set of type system related RFCs I want to propose for PHP 8.5. The objective is to fix a weird quirk of PHP's type system, where void lives in it

Re: [PHP-DEV] Deferred backtrace generation algorithm.

Hey Edmond, On 2.5.2025 10:14:37, Edmond Dantes wrote: Good day, everyone. In the neighboring thread Concept: Lightweight error channels, the topic of exception performance was discussed. The main issue is the immediate backtrace generation in the constructor, which can cause up to a 50% perfo

Re: [PHP-DEV] [RFC] [Discussion] Minor version compatibility

Hey Jorg, On 13.4.2025 23:07:07, Jorg Sowa wrote: I have collected all concerns, prepared an RFC for this change, and I'm opening discussion on its content: https://wiki.php.net/rfc/minor-version-compatibility Let me address some parts of the RFC: - The secondary vote #1 requires the same h

Re: [PHP-DEV] [RFC] [Discussion] Change default for zend.exception_ignore_args INI setting

Hey, On 10.4.2025 17:19:57, Tim Düsterhus wrote: Hi Am 2025-04-09 04:00, schrieb Andrew Lyons: The intent of this change is to make PHP installations safer by default and prevent the accidental release of sensitive information in stack traces. * RFC: https://wiki.php.net/rfc/exception_ignore

Re: [PHP-DEV] RFC: short and inner classes

Am 20.03.2025 um 15:51 schrieb Rob Landers :  On Wed, Mar 19, 2025, at 21:09, Bob Weinand wrote: On 19.3.2025 16:04:06, Rob Landers wrote: On Tue, Mar 18, 2025, at 03:37, Bob Weinand wrote: Okay, I see the point with LSP. I'm not sure whether we need to preserve LSP for that spe

Re: [PHP-DEV] RFC: short and inner classes

Am 20.03.2025 um 16:28 schrieb Rob Landers :  On Thu, Mar 20, 2025, at 16:12, Bob Weinand wrote: Am 20.03.2025 um 15:51 schrieb Rob Landers :  On Wed, Mar 19, 2025, at 21:09, Bob Weinand wrote: On 19.3.2025 16:04:06, Rob Landers wrote: On Tue, Mar 18, 2025, at 03:37, Bob Weinand wrote

Re: [PHP-DEV] RFC: short and inner classes

On 19.3.2025 16:04:06, Rob Landers wrote: On Tue, Mar 18, 2025, at 03:37, Bob Weinand wrote: Okay, I see the point with LSP. I'm not sure whether we need to preserve LSP for that specific scenario, but neither can I say that we should ignore it. (Effectively implementing LSP would

Re: [PHP-DEV] RFC: short and inner classes

Hey, On 17.3.2025 19:58:39, Rob Landers wrote: On Mon, Mar 17, 2025, at 19:05, Bob Weinand wrote: . The idea that extending the parent class doesnt no inherit the child classes doesnt make sense to me. As then if you extend a parent class and call a function of that class which could rely on

Re: [PHP-DEV] RFC: short and inner classes

Hey Rob, On 17.3.2025 17:53:26, Rob Landers wrote: On Mon, Mar 17, 2025, at 16:30, fennic log wrote: 2. As with any syntax change and new operator there needs to be very careful consideration, do we need a new operation, or could `::` if the parent is static or `->` if the class is initialized

Re: [PHP-DEV] RFC: short and inner classes

Hey Ilija, On 6.3.2025 23:20:37, Ilija Tovilo wrote: I would also like to echo what has been said about the :: operator, which feels out of place. I understand that \ comes with additional autoloading challenges, namely requiring a fallback autoloading strategy that currently does not conform to

Re: [PHP-DEV] RFC: short and inner classes

Hey Rob, On 6.3.2025 00:11:22, Rob Landers wrote: Hello PHP Internals, I'd like to introduce my RFC for discussion: https://wiki.php.net/rfc/short-and-inner-classes A small note on the Reflection section: it should include a method giving you an array of all contained ReflectionClasses: $r

Re: [PHP-DEV] RFC: short and inner classes

On 15.3.2025 00:21:32, Rowan Tommins [IMSoP] wrote: On 05/03/2025 23:11, Rob Landers wrote: I'd like to introduce my RFC for discussion: https://wiki.php.net/rfc/short-and-inner-classes As a user, I find the concept of inner classes quite confusing. However, I was looking at some code ea

Re: [PHP-DEV] RFC: short and inner classes

Hey Ilija, On 14.3.2025 17:09:40, Ilija Tovilo wrote: Hi Bob On Thu, Mar 13, 2025 at 11:36 PM Bob Weinand wrote: On 6.3.2025 23:20:37, Ilija Tovilo wrote: I would also like to echo what has been said about the :: operator, which feels out of place. I understand that \ comes with additional

Re: [PHP-DEV] [RFC] [Discussion] Optional interfaces

Hey Gina, On 12.3.2025 06:16:15, Gina P. Banyard wrote: On Tuesday, 11 March 2025 at 16:37, Juris Evertovskis wrote: Hey, Just a headsup that I plan to start the vote in a couple of days. Please let me know if there are concerns that might affect your stance on this proposal. https://wik

Re: [PHP-DEV] Re: RFC: short and inner classes

Hey Rob, On 14.3.2025 00:26:03, Rob Landers wrote: My biggest issue with `::` is that it gets weird: class Foo {   public class Bar {}   public const Bar = "";   public static function Bar() {} } echo Foo::Bar; // this is the constant new Foo::Bar(); // this is the class Foo::Bar(); // this is

Re: [PHP-DEV] Re: RFC: short and inner classes

Hey Rob, On 13.3.2025 21:46:49, Rob Landers wrote: On Thu, Mar 13, 2025, at 12:01, Tim Düsterhus wrote: Hi Am 2025-03-12 11:10, schrieb Rob Landers: > - Accessing inner classes is done via a new token: ":>" instead of > "::". I don't particularly like that. It is “invented syntax” and I don't

Re: [PHP-DEV] [RFC] PHP.net analytics

On 1.11.2024 22:41:29, Larry Garfield wrote: In a similar vein to approving the use of software, Roman Pronskiy asked for my help putting together an RFC on collecting analytics for PHP.net. https://wiki.php.net/rfc/phpnet-analytics Of particular note: * This is self-hosted, first-party only.

Re: [PHP-DEV] [RFC] Change behaviour of array sort functions to return a copy of the sorted array

On 20.10.2024 23:23:21, Ilija Tovilo wrote: Hi Bilge On Sun, Oct 20, 2024 at 10:30 PM Bilge wrote: I fail to see the logic of present tense = mutate, past tense = copy. At least there is a pattern to it, but I would have to look it up several times before it sunk in since it is not intuitive

Re: [PHP-DEV] No more RFC implementations during beta phase

On 24.9.2024 17:14:20, Christoph M. Becker wrote: Hi all, I want to suggest that we do not allow any RFC implementations to land during beta phase. In my opinion, the remaining time to thoroughly check and address possibly overlooked issues is way too short otherwise. For instance, the impleme

Re: [PHP-DEV] Debug Build Container Image for GitHub Packages

On 3.9.2024 02:18:30, Ben Ramsey wrote: On Sep 2, 2024, at 18:53, Bob Weinand wrote: On 3.9.2024 01:44:21, Ben Ramsey wrote: On Sep 2, 2024, at 08:11, Go Kudo wrote: Hi Internals. PHP currently does not provide official container images. Given that DockerHub adequately maintains these and

Re: [PHP-DEV] Debug Build Container Image for GitHub Packages

On 3.9.2024 01:44:21, Ben Ramsey wrote: On Sep 2, 2024, at 08:11, Go Kudo wrote: Hi Internals. PHP currently does not provide official container images. Given that DockerHub adequately maintains these and considering the maintenance costs, we haven't felt the need to change the status quo.

Re: [PHP-DEV] [RFC] [Discussion] Using and Mentioning Third-party Packages in PHP Documentation and Web Projects

Hey Jim, On 26.8.2024 19:44:18, Jim Winstead wrote: Hi, Another RFC around process: https://wiki.php.net/rfc/web-and-doc-use-not-endorsement Feedback would be appreciated. My intention is to start voting on September 9th unless there is still ongoing discussion. Thanks. Jim Thanks for

Re: [PHP-DEV] [RFC] Default expression

Hey Jordi, On 26.8.2024 13:55:52, Jordi Boggiano wrote: One question (sorry if someone already asked, I scanned the thread but it is getting long..): Taking this example from the RFC:     function g($p = null) {         f($p ?? default);     } Could you go one step further and use default by

Re: [PHP-DEV] [RFC] Default expression

On 26.8.2024 00:31:57, Rowan Tommins [IMSoP] wrote: I'm not an expert on parsers, and never claimed to be, so it's not particularly surprising to me that I've overlooked a reason why "expr ?: default" can't be included without also including "default ?: expr", and will just have to take your wo

Re: [PHP-DEV] State of Generics and Collections

Hey Arnauld, On 20.8.2024 15:01:28, Arnaud Le Blanc wrote: Hi Bob, On Tue, Aug 20, 2024 at 12:18 AM Bob Weinand wrote: The fluid Arrays section says "A PoC has been implemented, but the performance impact is still uncertain". Where may I find that PoC for my curiosity? I'm

Re: [PHP-DEV] State of Generics and Collections

On 20.8.2024 03:31:05, Larry Garfield wrote: On Mon, Aug 19, 2024, at 5:16 PM, Bob Weinand wrote: Regarding the Collections PR, I personally really don't like it: • It implements something which would be trivial if we had reified generics. If this ever gets merged, and generics happen

Re: [PHP-DEV] State of Generics and Collections

On 19.8.2024 19:08:32, Derick Rethans wrote: Hi! Arnaud, Larry, and I have been working on an article describing the state of generics and collections, and related "experiments". You can find this article on the PHP Foundation's Blog: https://thephp.foundation/blog/2024/08/19/state-of-generics-

Re: [PHP-DEV] Request for opinions: bug vs feature - change intokenization of yield from

Hey Christoph, Am 19.07.2024 um 00:51 schrieb Christoph M. Becker : Hi Bob! On 18.07.2024 at 15:41, Bob Weinand wrote: Moreover, it can - at least - be worked around in tooling by special casing the T_YIELD_FROM token and extracting the comment from the raw parsed string: var_dump

Re: [PHP-DEV] Request for opinions: bug vs feature - change in tokenization of yield from

Am 18.07.2024 um 01:15 schrieb Juliette Reinders Folmer :  Hi all, I recently discovered a change was made to the Tokenizer in PHP 8.3.0 which now allows for a comment to exist between the `yield` and `from` keyword from the `yield from` keyword. Before PHP 8.3, this was a parse error. This

Re: [PHP-DEV] Consider removing autogenerated files from tarballs

On 29.3.2024 23:31:26, Daniil Gentili wrote: In light of the recent supply chain attack in xz/lzma, leading to a backdoor in openSSH (https://www.openwall.com/lists/oss-security/2024/03/29/4), I believe that it would be a good idea to remove the huge attack surface offered by the pre-generated

Re: [PHP-DEV] Re: [RFC] [Discussion] [VOTE] Rounding Integers as int

Hey Marc, On 18.3.2024 08:53:01, Marc Bennewitz wrote: Hi Bob, On 17.03.24 14:59, Bob Weinand wrote: On 17.3.2024 13:23:04, Marc Bennewitz wrote: Hello internals, I have opened the vote for the "Rounding Integers as int" RFC: https://wiki.php.net/rfc/integer-rounding Do to East

[PHP-DEV] Re: [RFC] [Discussion] [VOTE] Rounding Integers as int

On 17.3.2024 13:23:04, Marc Bennewitz wrote: Hello internals, I have opened the vote for the "Rounding Integers as int" RFC: https://wiki.php.net/rfc/integer-rounding Do to Easter weekend the vote will run for two weeks and two days until Tue the 2nd of April 2024. Best regards, Marc Bennew

Re: [PHP-DEV] [RFC] [Discussion] nameof

> Am 14.01.2024 um 23:58 schrieb Robert Landers : > > Hello Internals, > > After much thought and deliberation, I've updated the nameof RFC > (https://wiki.php.net/rfc/nameof) to reflect most of this discussion > and refine a few edge cases regarding objects. TL;DR: there are a few > rules rega

Re: [PHP-DEV] [VOTE] [RFC] Final-by-default anonymous classes

> Am 15.01.2024 um 11:57 schrieb Nicolas Grekas : > > Hi Daniil, > > I've opened voting for the final-by-default anonymous classes RFC: >> https://wiki.php.net/rfc/final_by_default_anonymous_classes >> > > I voted against the proposal because as I mentioned in the previous thread > on the sam

Re: [PHP-DEV] First-class callable partial application

> Am 14.03.2023 um 10:16 schrieb Rowan Tommins : > > On 13/03/2023 20:44, Larry Garfield wrote: >> As has been discussed numerous times, all of the most used array functions >> need to be redesigned to work with iterables, and in many cases make more >> sense. That would be a natural time to

Re: [PHP-DEV] PHP code refactoring (was: include cleanup)

Hey Max and Dmitry, > Am 28.02.2023 um 23:34 schrieb Dmitry Stogov : > > On Wed, Mar 1, 2023 at 1:21 AM Max Kellermann wrote: > >> On 2023/02/28 22:31, Dmitry Stogov wrote: >>> https://github.com/php/php-src/commit/0270a1e54c0285fa3c89ee2b0120073ef57ab5fa >> >> This kind of change was favored

Re: [PHP-DEV] [PHP_DEV] [RFC] Add file_descriptor() function

> Am 16.01.2023 um 16:01 schrieb G. P. B. : > > Hello internals, > > I would like to start the discussion about the "Add file_descriptor() > function" RFC: > https://wiki.php.net/rfc/file-descriptor-function > > This RFC proposes the addition of the file_descriptor() function to > retrieve the

[PHP-DEV] [RFC][Vote] Destructuring Coalesce

Hey, I've just opened the vote on the https://wiki.php.net/rfc/destructuring_coalesce RFC. It will end on November 21. Bob

Re: [PHP-DEV] [RFC] Destructuring Coalesce

> Am 03.11.2022 um 20:55 schrieb Tim Düsterhus : > > Hi > > On 10/16/22 23:11, Bob Weinand wrote: >> I've written a small RFC about adding coalesce ability to list() >> destructuring. >> This should enhance the ability to easily, concisely and readably >

Re: [PHP-DEV] [RFC] Destructuring Coalesce

Hey, > Am 16.10.2022 um 23:56 schrieb David Rodrigues : > > I like it! > > But what should happen if: > > [ $a ?? '123', $b ] = []; $a is assigned 123, $b emits undefined key error. > [ $a ?? '123', $b ] = [ 1 ]; $a is assigned 1, $b emits undefined key error. > [ $a ?? '123', $b ] = [ 1, 2

Re: [PHP-DEV] [RFC] Destructuring Coalesce

> Am 16.10.2022 um 23:11 schrieb Bob Weinand : > > Hey, > > I've written a small RFC about adding coalesce ability to list() > destructuring. > > This should enhance the ability to easily, concisely and readably destructure > arrays with default value

[PHP-DEV] [RFC] Destructuring Coalesce

Hey, I've written a small RFC about adding coalesce ability to list() destructuring. This should enhance the ability to easily, concisely and readably destructure arrays with default values. https://wiki.php.net/rfc/destructuring_coalesce Bob

Re: [PHP-DEV] [RFC] Undefined Variable Error Promotion

Hey Mark, For me, there's a fundamental shortcoming of this proposal: - You cannot opt out. Currently, as you describe in your RFC, it is perfectly possible, to opt into making this category of errors fail hard (throw an exception in an error handler). However, should your RFC pass, it is not

Re: [PHP-DEV] [VOTE] User Defined Operator Overloads

> Am 03.01.2022 um 01:13 schrieb Jordan LeDoux : > > Hello internals, > > I've opened voting on > https://wiki.php.net/rfc/user_defined_operator_overloads. The voting will > close on 2022-01-17. > > To review past discussions on this RFC and the feature in general, please > refer to: > > - http

Re: [PHP-DEV] [RFC] Locale-independent case conversion

> Am 04.10.2021 um 12:08 schrieb Nikita Popov : > > On Thu, Sep 23, 2021 at 8:32 AM Tim Starling > > wrote: > >> Please consider my RFC for locale-independent case conversion. >> >> https://wiki.php.net/rfc/strtolower-ascii >> https://github.com/php/php-src/pull/

Re: [PHP-DEV] [Vote] Pipe operator v2

Hey Larry, there's still ongoing discussion on the semantics, and mirroring implementation defined semantics from the implementation into the RFC is not the way to go. The RFC should discuss reasons of why semantics were chosen and the implementation then be decided upon it. Describing it as "d

Re: [PHP-DEV] Disable interactive mode (-a) if readline not available

> Am 12.05.2021 um 10:12 schrieb Nikita Popov : > > Hi internals, > > If the readline extension is enabled, PHP provides an interactive shell > under -a. If it is not enabled, it falls back to an "interactive mode" > (yes, the difference between "interactive shell" and "interactive mode" is > imp

Re: [PHP-DEV] [VOTE] Dump results of expressions in `php -a`

Hey Tyson, > Am 02.02.2021 um 03:35 schrieb tyson andre : > > Hi Bob Weinand, > >>> Am 20.01.2021 um 01:55 schrieb tyson andre : >>> >>> Hi internals, >>> >>> Voting has started on >>> https://wiki.php.net/rfc/readline_intera

Re: [PHP-DEV] [VOTE] Dump results of expressions in `php -a`

> Am 20.01.2021 um 01:55 schrieb tyson andre : > > Hi internals, > > Voting has started on > https://wiki.php.net/rfc/readline_interactive_shell_result_function > on 2021-01-19, and ends on 2021-02-02. > > This RFC proposes to dump the results of non-null expressions using > var_dump/var_expor

Re: [PHP-DEV] [RFC] Enumerations, Round 2

> Am 29.01.2021 um 18:15 schrieb Larry Garfield > : > > And we're back again. The RFC has been updated with a steady stream of > smaller improvements based on feedback and testing, and is now in its Final > Form(tm) (we think). The only major change worth noting is that we re

Re: [PHP-DEV] [RFC][Proposal] Renamed parameters

> Am 24.07.2020 um 16:11 schrieb Benjamin Eberlei : > > On Fri, Jul 24, 2020 at 4:00 PM Chris Riley wrote: > >> Hi all, >> >> Following up from this I've created a draft RFC: >> https://wiki.php.net/rfc/renamed_parameters will move to in discussion >> once >> I've ensured everything important h

Re: [PHP-DEV] [RFC][VOTE] debug_backtrace alternative as an array of StackFrame objects

> Am 22.07.2020 um 09:10 schrieb Côme Chilliet > : > > Le Tue, 21 Jul 2020 13:52:39 +0200, > Michał Marcin Brzuchalski a écrit : >> Voting opened 2020-07-21 and closes 2020-08-04. >> >> Link to the RFC https://wiki.php.net/rfc/stack-frame-class#vote > > Hello, > > Can people voting no explain

Re: [PHP-DEV] [RFC] [VOTE] Saner numeric strings

> Am 17.07.2020 um 11:30 schrieb Nikita Popov : > > On Fri, Jul 17, 2020 at 11:27 AM Bob Weinand <mailto:bobw...@hotmail.com>> wrote: > Hey George, > > while I agree with your RFC in general, changing the autocast behavior of the > empty string is not accepta

Re: [PHP-DEV] [RFC] [VOTE] Saner numeric strings

Hey George, while I agree with your RFC in general, changing the autocast behavior of the empty string is not acceptable for me. Empty strings often are the output of non-existing things, like default value of a text field in a DB, when reading files not filled with inputs yet etc. It should e

Re: [PHP-DEV] [RFC][Discussion] Change terminology to ExcludeList

> Am 18.06.2020 um 20:24 schrieb Lynn : > > > > On Thu, Jun 18, 2020 at 3:38 PM Bob Weinand <mailto:bobw...@hotmail.com>> wrote: > P.s. And to be honest, I've never heard from a dark-skinned person that they > felt actually oppressed by words like blacklist

Re: [PHP-DEV] [RFC] [DISCUSSION] Make constructors and destructors return void

sometimes_ it is justified. Only because something mostly is a bad idea, it is not always. Also note that other languages completely forbid manual ctor calls. But PHP doesn't (and for good reason, like after using ReflectionClass::newInstanceWithoutConstructor). Bob > Best regard

Re: [PHP-DEV] [RFC][Discussion] Change terminology to ExcludeList

> Am 18.06.2020 um 00:36 schrieb Jakob Givoni : > To repeat what has been said many times over now: It's when "black" is > associated with "bad" in a composite term like "blacklist" we should > consider being considerate of a group of people who actually have skin > of that color. > > Best, > Jako

Re: [PHP-DEV] [RFC] [DISCUSSION] Make constructors and destructors return void

> Am 17.06.2020 um 01:10 schrieb Benas IML : > > Hey internals, > > This is a completely refined, follow-up RFC to my original RFC. Based on the > feedback I have received, this PR implements full validation and implicitly > enforces `void` rules on constructors/destructors while also allowing to

Re: [PHP-DEV] Re: [RFC] Named arguments

> Am 29.05.2020 um 21:02 schrieb Larry Garfield : > > On Fri, May 29, 2020, at 9:32 AM, Nikita Popov wrote: >> On Tue, May 5, 2020 at 3:51 PM Nikita Popov wrote: >> >>> Hi internals, >>> >>> I've recently started a thread on resurrecting the named arguments >>> proposal (https://externals.io/me

Re: [PHP-DEV] [RFC] Amendments to Attributes

> Am 22.05.2020 um 13:08 schrieb Nikita Popov : > > On Wed, May 20, 2020 at 7:08 PM Benjamin Eberlei > wrote: > >> 2. Rename PhpAttribute to Attribute in global namespace (independent of the >> namespace RFC) > > As was mentioned in one of the previous discussions, we expect that PHP is > going

Re: [PHP-DEV] Re: Making all Traversables an Iterator or IteratorAggregate

Hey Sara, > Am 12.05.2020 um 14:49 schrieb Sara Golemon : > > On Tue, May 12, 2020 at 3:26 AM Nikita Popov wrote: >> // WeakMap::getIterator(): Iterator >> ZEND_METHOD(WeakMap, getIterator) >> { >>if (zend_parse_parameters_none() == FAILURE) { >>return; >>} >>zend_create_inte

Re: [PHP-DEV] [RFC] Keep type of reference params

> Am 04.05.2020 um 10:53 schrieb Manuel Canga : > > Hi internals, > > > > I would like to present a possible new RFC( "keep type of reference params" ) > for your > > consideration. > > > > Firstly, an example: > > > > ``` > > > > > function my_array_shift( array & $array ) { > >

Re: [PHP-DEV] [VOTE] match expression

> Am 28.04.2020 um 12:48 schrieb Rowan Tommins : > > On Tue, 28 Apr 2020 at 11:19, Ilija Tovilo wrote: > >>> for the control-flow statement, it feels awkward and not in >>> keeping with the rest of the language. If they were separate proposals, >> the >>> statement would probably end up looki

Re: [PHP-DEV] [VOTE] match expression

> Am 25.04.2020 um 12:39 schrieb Ilija Tovilo : > > Hi internals > > I have opened the voting on the match expression RFC. It will end on > 9th of May, 2020. > https://wiki.php.net/rfc/match_expression > > Here are the last changes: > > In the last update I mentioned allowing return values in b

Re: [PHP-DEV] [RFC] Mixed type

it. Bob > Am 24.04.2020 um 14:11 schrieb Bob Weinand : > > Hey Dan, > > this, I consider one of the few concepts which should never make it into PHP. > > In particular, the main problem with mixed is that it is a very easy "I have > no idea how to type that properly, s

Re: [PHP-DEV] [RFC] Mixed type

Hey Dan, this, I consider one of the few concepts which should never make it into PHP. In particular, the main problem with mixed is that it is a very easy "I have no idea how to type that properly, so just let's use mixed". And really, in general, except for some debug functions, mixed is just

Re: [PHP-DEV] Warn when declaring required parameter after optional one

Hey, While I generally agree that it likely is a bug in new code, I would rather deprecate it than warn or even error: the change would make it impossible to retain a type without warning while preserving compatibility with an old PHP version and making incremental migrations harder (would then

Re: [PHP-DEV] Inline switch as alternative to nested inline conditional

Am 16.10.2019 um 21:19 schrieb Claude Pache mailto:claude.pa...@gmail.com>>: Le 16 oct. 2019 à 19:11, Bob Weinand mailto:bobw...@hotmail.com>> a écrit : Am 16.10.2019 um 03:46 schrieb David Rodrigues mailto:david.pro...@gmail.com>>: Hello. I like to suggests a discussion

Re: [PHP-DEV] Inline switch as alternative to nested inline conditional

> Am 16.10.2019 um 03:46 schrieb David Rodrigues : > > Hello. I like to suggests a discussion about a FR to make possible to > inline switch, as an alternative to nested inline conditionals. > > $value = switch (expr()) { >case A1: return A2; >case B1: return B2; >default: return C; >

Re: [PHP-DEV] Re: Bringing Peace to the Galaxy

Hey Zeev, > Am 09.08.2019 um 19:44 schrieb Zeev Suraski : > > On Fri, Aug 9, 2019 at 7:44 PM Dan Ackroyd wrote: > >> On Fri, 9 Aug 2019 at 17:10, Zeev Suraski wrote: >>> >>> we’re discussing whether it makes sense to introduce a sister language >> to PHP. >> >> Zeev also wrote: >>> It will t

Re: [PHP-DEV] [RFC] Explicit call-site send-by-ref syntax

> Am 30.07.2019 um 17:14 schrieb Zeev Suraski : > > On Tue, Jul 30, 2019 at 6:10 PM Levi Morrison > wrote: > >> On Mon, Jul 29, 2019, 10:55 PM Zeev Suraski wrote: >> >> > I think ignoring people is totally acceptable behaviour on this list. May I >> remind you that in the not distant past thi

Re: [PHP-DEV] [RFC] [Vote] Change the precedence of the concatenation operator

> Am 01.05.2019 um 00:41 schrieb Bob Weinand : > > Hey, > As announced yesterday, I'm now starting the vote on this RFC. > > I'm confident that the impact is really that minimal that a relatively quick > deprecation and change path is preferred

[PHP-DEV] [RFC] [Vote] Change the precedence of the concatenation operator

Hey, As announced yesterday, I'm now starting the vote on this RFC. I'm confident that the impact is really that minimal that a relatively quick deprecation and change path is preferred. https://wiki.php.net/rfc/concatenation_precedence The vote ends on May 15. Thanks, Bob

Re: [PHP-DEV] [RFC] Change the precedence of the concatenation operator

Am 25.04.2019 um 11:52 schrieb Nikita Popov mailto:nikita@gmail.com>>: On Thu, Mar 28, 2019 at 2:33 PM Bob Weinand mailto:bobw...@hotmail.com>> wrote: Hey, I feel like concatenation having the same precedence than addition and subtraction is promoting programmers to make mist

[PHP-DEV] [RFC] Change the precedence of the concatenation operator

Hey, I feel like concatenation having the same precedence than addition and subtraction is promoting programmers to make mistakes. Albeit typically easy to catch ones, it is a quality of life change at least. Hence I'm proposing a RFC changing the precedences: https://wiki.php.net/rfc/concatena

Re: [PHP-DEV] RFC Draft: Comprehensions

> Am 10.03.2019 um 22:44 schrieb Larry Garfield : > > Hello, peoples. I know it's been discussed once or twice before on the list, > many years ago, but not recently. I therefore feel OK putting forth the > following draft proposal for Comprehensions, aka "compact generators", in PHP: > > htt

Re: [PHP-DEV] Alternative voting reform: Streamlining the RFC process

> Am 03.02.2019 um 06:18 schrieb Zeev Suraski : > >> -Original Message- >> From: Nikita Popov >> Sent: Saturday, February 2, 2019 6:24 PM >> To: PHP internals >> Subject: [PHP-DEV] Alternative voting reform: Streamlining the RFC process >> >> Hi internals, >> >> After discussing the to

[PHP-DEV] [RFC] [VOTE] Typed properties v2

Hey, As announced, we are starting the vote on typed properties today. The voting period is two weeks, until sometime in the evening on Tuesday 25-09-2018. Please find the RFC at https://wiki.php.net/rfc/typed_properties_v2. Bob and Nikita -- PHP Internals - PHP Runtime Development Mailing Lis

Re: [PHP-DEV] [RFC] Pre-Vote: Typed properties

Am 08.09.2018 um 09:51 schrieb Marco Pivetta mailto:ocram...@gmail.com>>: Hey Bob, Did the implementation change a lot since it was last successfully tested, or is it mostly stabilization changes? Greets, Marco On Fri, 7 Sep 2018, 23:19 Bob Weinand, mailto:bobw...@hotmail.com>>

[PHP-DEV] [RFC] Pre-Vote: Typed properties

Hey, Due to the mailing list downtime this has been delayed a bit ... I'd like to push the Typed properties RFC forward to a vote soon: https://wiki.php.net/rfc/typed_properties_v2 Unless there are major objections, I will start the vote on Tuesday for two weeks. Bob

RE: [PHP-DEV] [RFC] Typed Properties

From: nicolas.gre...@gmail.com On Behalf Of Nicolas Grekas Sent: Thursday, June 21, 2018 18:51 To: Bob Weinand Cc: Nikita Popov ; PHP internals Subject: Re: [PHP-DEV] [RFC] Typed Properties something like a ReflectionReference class, which will give you the referencing properties via

RE: [PHP-DEV] [RFC] Typed Properties

> From: Patrick ALLAERT > Sent: Thursday, June 21, 2018 18:25 > To: Nikita Popov > Cc: PHP internals > Subject: Re: [PHP-DEV] [RFC] Typed Properties > > My only concern is about regular variables, not bound to any classes. Isn't > that a little bit inconsistent that classes properties could be t

RE: [PHP-DEV] [RFC] Typed Properties

Hey Larry, > From: Larry Garfield > Sent: Thursday, June 21, 2018 18:17 > To: internals@lists.php.net > Subject: Re: [PHP-DEV] [RFC] Typed Properties > Questions along the way: > > * There was at one point in time a related RFC regarding property accessors > (dedicated getter/setter methods for

RE: [PHP-DEV] [RFC] Typed Properties

> From: nicolas.gre...@gmail.com On Behalf Of > Nicolas Grekas > Sent: Thursday, June 21, 2018 16:08 > To: Nikita Popov > Cc: PHP internals > Subject: Re: [PHP-DEV] [RFC] Typed Properties > > Hi Nikita, Bob, > > I anticipate one case on Symfony VarDumper that will break on typed > references:

RE: [PHP-DEV] [RFC] Typed Properties

Hey Sara, > From: p...@golemon.com On Behalf Of Sara Golemon > Sent: Thursday, June 21, 2018 15:43 > To: Nikita Popov > Cc: PHP internals > Subject: Re: [PHP-DEV] [RFC] Typed Properties > > On Wed, Jun 20, 2018 at 4:59 PM, Nikita Popov > wrote: > > Finally, while this RFC currently targets PH

RE: [PHP-DEV] [RFC] Typed Properties

> From: Marco Pivetta > Sent: Thursday, June 21, 2018 01:10 > To: Nikita Popov > Cc: PHP Internals List > Subject: Re: [PHP-DEV] [RFC] Typed Properties > > Hi Nikita, Bob, > > On Wed, 20 Jun 2018, 23:59 Nikita Popov, wrote: > > > Hi internals, > > > > Bob and I would like to present a new ty

[PHP-DEV] Re: 7.2 behavior break, Bug #74836 isset on zero-prefixed numeric indexes in array broken

Am 03.07.2017 um 09:03 schrieb Dmitry Stogov mailto:dmi...@zend.com>>: Hi, Please take a look at https://bugs.php.net/bug.php?id=74836 What is the best option to fix this? The most consistent way, from my point of view - disabling zero-prefexed numeric strings in all cases, but this is a new b

Re: [PHP-DEV][RFC][VOTE] Allow abstract function override

> Am 28.03.2017 um 06:58 schrieb Marco Pivetta : > > Voted "no" because of this paragraph: > >> This RFC proposes to allow this, even if it has very few uses, and > because there is no reason to disallow a compatible redefinition. > > I couldn't see a use-case. > > In addition to that, this br

Re: [PHP-DEV] [RFC][Discuss] Arrow Functions

> Am 31.01.2017 um 19:41 schrieb Christoph M. Becker : > > On 31.01.2017 at 19:16, Michael Morris wrote: > >> On Tue, Jan 31, 2017 at 12:29 PM, Larry Garfield >> wrote: >> >>> My question is why there's no mention of HHVM short closures, or the >>> previous RFC to take that approach. See: >>>

Re: [PHP-DEV] [RFC][Discuss] Arrow Functions

> Am 31.01.2017 um 21:45 schrieb Andrea Faulds : > > Hi Marc, > > Marc Bennewitz wrote: >> - Also I like the "use" keyword you have to define your variables >> >>-> Would it be helpful to allow "function () use (*) {}" to inline >> all available variables? > > I did think of that, but it'

Re: [PHP-DEV] [RFC][Discuss] Arrow Functions

Hey, > Am 31.01.2017 um 11:23 schrieb Michael Wallner : > > On 31/01/17 05:53, Stephen Reay wrote: >> Hi Andrea, All, >> >>> On 31 Jan 2017, at 08:12, Andrea Faulds wrote: >>> >>> Is it necessary to introduce a new keyword, fn? >>> >>> I think you'd get a similar benefit from: >>> >>> func

Re: [PHP-DEV] Change in type-hint representation

> Am 11.01.2017 um 17:37 schrieb Dmitry Stogov : > > The patch was updated according to feedback: added comments, better names and > encapsulation, less magic, better code reuse, keep a free bit in zend_type > for future extension. >

  1   2   3   4   >