Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:102642 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 78667 invoked from network); 7 Jul 2018 23:35:25 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Jul 2018 23:35:25 -0000 Authentication-Results: pb1.pair.com header.from=php@golemon.com; sender-id=softfail Authentication-Results: pb1.pair.com smtp.mail=php@golemon.com; spf=softfail; sender-id=softfail Received-SPF: softfail (pb1.pair.com: domain golemon.com does not designate 209.85.208.51 as permitted sender) X-PHP-List-Original-Sender: php@golemon.com X-Host-Fingerprint: 209.85.208.51 mail-ed1-f51.google.com Received: from [209.85.208.51] ([209.85.208.51:40916] helo=mail-ed1-f51.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id AD/56-55607-C3E414B5 for ; Sat, 07 Jul 2018 19:35:24 -0400 Received: by mail-ed1-f51.google.com with SMTP id e19-v6so11126259edq.7 for ; Sat, 07 Jul 2018 16:35:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=golemon-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-transfer-encoding; bh=X2LJKLfsx3jMvgZkQBTG36Z/7PvaIAnzBtWQ75HLvJU=; b=XetiGFGuG7eXuD2Oc+sfHbVlLJMXPItZXveL+lT0k619Sbjcc5AZlKEZFm0vfgcXDh 8lMakMvmDn3JS/kV2nxSuxkyqNBp1SXIaqyj8E2xUOq7CHchzsRKmmfJuBwEEWTa8ghs 8uVMqUiL4JLPRFElucQAQ6gtwzOZmonLY6mIVkgg0sVdgFCmDscRQzX47sDlCSdvM50H j8kZoIjOQ/NyWp4/sXHRFYe72hhcf77bghe/B+1+CR5Tk3WGm6VRFYDTBMzTGHEHgyhs bs6NKr/J18AuMYR7/OVmR2iDngtu/0oX6hgS2YQa1dqQXxXsCErWd4u9YDD+4+e/8UPI thpA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc:content-transfer-encoding; bh=X2LJKLfsx3jMvgZkQBTG36Z/7PvaIAnzBtWQ75HLvJU=; b=tyZc8XG7E0vKnu42PiHdbpTQwt5J7DBEIDJz0nDVjixXxYWwbgyNCu6YhHpZcITIc1 xRJiNBrWr8+PC/SV11kTUTS7w9GdkG3cuubddkAA7TlemPunvBGxaqLZXZgYv9euBdR4 YqFI2muLY1tLnaz+QoLOp7tlbg+PgqaMe5f5Cg28e6991q0PTmmpkJM7g250Q/wDCjGS 7+Z3BjYMGWm/dKJWyT4Ck0UtnsMh4Zef4F6x6dNlOMIqlapLXQpN43NzNaG7sc3W+DzF ibnl+liOrJOi4safKDHLf9qYc/yj2DGZJj2wRkG9ciYcEFCLmGsSNyxQlsKqEDPAgrGH hMzw== X-Gm-Message-State: APt69E2s4fF6KIYXTr1riuWs25UVqbfaMQstJBEMM1n/KoSVgdJ2tXaA OH98ilWG3nCqebWgc0tpWU0f9IZ7LYrc50RU5DuJeg== X-Google-Smtp-Source: AAOMgpfhRgX/YQRCRfYkp3BvTodSXFuIYa3LdyomBpHm1HuEayn1dhx1d+3Tu0Qn3JhKi3dO2j8hKRE0zwUg3Jtu9xs= X-Received: by 2002:a50:8f23:: with SMTP id 32-v6mr16316100edy.192.1531006521844; Sat, 07 Jul 2018 16:35:21 -0700 (PDT) MIME-Version: 1.0 Sender: php@golemon.com Received: by 2002:a50:8617:0:0:0:0:0 with HTTP; Sat, 7 Jul 2018 16:35:21 -0700 (PDT) X-Originating-IP: [173.68.96.220] In-Reply-To: <5cc6a95f-0033-3a8e-2cd6-dc47d0a41730@gmx.de> References: <10e578d7-7a24-3ca0-ca0d-d5ed1a39dca3@telia.com> <80a8f588-05a3-48e5-bf40-bf1685b3105e@gmx.de> <5cc6a95f-0033-3a8e-2cd6-dc47d0a41730@gmx.de> Date: Sat, 7 Jul 2018 19:35:21 -0400 X-Google-Sender-Auth: x23IR8H-o7uPfTqtkZaNOx457BY Message-ID: To: "Christoph M. Becker" Cc: Nikita Popov , "stas@php.net" , =?UTF-8?Q?Bj=C3=B6rn_Larsson?= , Dan Ackroyd , Stanislav Malyshev , Marco Pivetta , PHP internals Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] [RFC] Typed Properties From: pollita@php.net (Sara Golemon) On Fri, Jul 6, 2018 at 4:46 PM, Christoph M. Becker wro= te: > Why should we have 2 additional alphas? In my opinion, a single > additional alpha is sufficient, and it is really important not to add > yet further features. > Because in the best case scenario (with a single extra alpha), the RFC is ready now, and the vote for it opens immediately. After two weeks, we get a yes vote and we'll be right on the edge of ready for FF/beta1. Adding that fifth alpha gives us breathing room for something short of idealized circumstances. On Sat, Jul 7, 2018 at 5:12 PM, Zeev Suraski wrote: > First, it may be a personal thing, but I feel that the flexibility toward= s adding > this is very contrasty with the inflexibility shown as we headed towards = the > PHP 7.0 feature freeze - inflexibility that resulted in a rushed (and IMH= O wrong) > decision regarding how to implement the non-strict types. > Actually, I think Typed Props are being rushed as well, and I'm not pleased with it, but I can also see the writing on the wall and want to minimize the impact of that hurry (hence, pushing the timeline out rather than having things land weeks into the beta cycle). > For the record - as I said back then - I think that the right way is to = be flexible - > the dates are just dates, and are - in all honesty - not that important -= it=E2=80=99s the severe > inconsistency that bothers me. > I agree that dates are just dates, but blithely eroding the pre-release cycle without pushing the GA date out isn't saying "dates are dates", it's saying "RC testing doesn't matter". I just want 7.3 to get as much baking in time as earlier releases got. > Secondly, and somewhat related - typed properties isn't a small feature. > It is, in fact, a pretty huge one. Making exceptions for a fairly minor = feature > or some extra deprecation is one thing. Making an exception for somethin= g > as fundamental as that feels wrong. > Agreed, and why I haven't decided on a "yes" vote. Again, I'm not pushing for this feature, I'm pushing for our pre-release cycle suffering as little damage as I can manage to protect it from. > Even though Nikita's proposal and implementation look pretty solid, > something as fundamental as that should go through a substantial > active discussion period (which didn't really happen here as it wasn't > clear whether this was headed for an exceptional 7.3 addition or not) - > I'm working on the assumption that Niki still plans to bring this to vote. Perhaps he's decide it needs to wait and this whole discussion of extra alphas is moot. That's why I sent an email about the subject. > and independently - should perhaps go hand-in-hand with fixing the > flaws of the non-strict types - something we can do in PHP 8. > If we do the latter, then perhaps, just perhaps, we can introduce it > hand-in-hand with typed variables - and if we do, it will be sensible > to do it at the same time and not in a gradual rollout. > And that's a decision we need to make, NOW. We need to know in the next 10 days if we're going to move forward with a 7.3 that doesn't contain TP, or if we're going to push out the betas until we can solidify it. Waiting to make that decision is making a decision by default (almost as bad as making the wrong decision). > Personally, I think even independently of typed variables, typed properti= es feel like an 8.0 feature, not a 7.x feature. > I probably agree with you on that. (Again, still undecided). -Sara