Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:102346 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 74729 invoked from network); 21 Jun 2018 14:50:21 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Jun 2018 14:50:21 -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 74.125.82.54 as permitted sender) X-PHP-List-Original-Sender: php@golemon.com X-Host-Fingerprint: 74.125.82.54 mail-wm0-f54.google.com Received: from [74.125.82.54] ([74.125.82.54:39894] helo=mail-wm0-f54.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 03/B0-32156-82BBB2B5 for ; Thu, 21 Jun 2018 10:50:19 -0400 Received: by mail-wm0-f54.google.com with SMTP id p11-v6so6644877wmc.4 for ; Thu, 21 Jun 2018 07:50:16 -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; bh=i02mL5Gt5WSpD9EKticXJ4CTtwwunU5gncGobdsZlIg=; b=faPv6E+541aNG7IKvpCRC1Uxubmzlv4uq656n5r0CreenwrG7KuQpzYdY2g8RPOriN BlpI+SGpjPW7d2eYOPYCrV9WVfFi98ezyi9JdQrAcgTX2lH6L9x97VojMpwpZ23nuD+/ GHn3XQhFVPdjYc0ath4suSG2PebXWWgm/VmwSopUQH2LlGR4vDETf1XsUPdz39gshdsg sOaiAD4z9NYfwSfYJxXsu4YeSfGxLbhf85r6SzlwmXGa1MLVZrtcyJNYGkOGEZnNaW4S Qwjh7dMz8SaZIMuqaPBD9g3gqTXEkmqRXADdU6tJ9YImJlaN7iL1mK4VG39yoQwQjjik kD4A== 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; bh=i02mL5Gt5WSpD9EKticXJ4CTtwwunU5gncGobdsZlIg=; b=MFbSrVl9RGGTpcL7hLyC7cfALPcz7MYLFDp/uqkmhdrqjxibjgbDMhU0LIPitUc7UT hmJE1JCvnUQXoUZ9OaTzU4iS9lA5+IVuO8ToOl0eDy42zMRc+/s0bSLss2XN/PgtPJcB pIy75MBKYUlfaOV9c3iy9+sPENKErW5xpW76/uedGkTKEQkIZ5AL0A+WVGSGrEvCfNgC m6/grImqD1JmaXC15hqVZUiBl+S29n17wtrAqPzaiDqpJGXQQ2a8fjvsZQRDHtFkVkEM i0nOXRUDiurrDwTtNitVXEedc4rKwsIINpQfx7PGfh4pTBUvFQTvrK3hswnV0XGrgX8g XXSg== X-Gm-Message-State: APt69E30+mNH6W1rctsvMZgWFKZxKrLHLZDKb/2enNh28jD7tIHnXBhx TSzMPhqGv5Wr27kLPvNQqKZSTl0Hq2G4GlHfKzlMwQ== X-Google-Smtp-Source: ADUXVKJt8Ay8MAPC5hBrS3HKQ2ByaCVbP+5Ea0hs3Hmd81g6UApLxRSn+U2bKF5+f+SMg330/UtHdoDlaOe5oRKhI5Y= X-Received: by 2002:a50:9b5b:: with SMTP id a27-v6mr22163081edj.60.1529592613809; Thu, 21 Jun 2018 07:50:13 -0700 (PDT) MIME-Version: 1.0 Sender: php@golemon.com Received: by 2002:a50:8625:0:0:0:0:0 with HTTP; Thu, 21 Jun 2018 07:50:13 -0700 (PDT) X-Originating-IP: [73.210.228.160] In-Reply-To: References: Date: Thu, 21 Jun 2018 09:50:13 -0500 X-Google-Sender-Auth: 1oA_43rpQ44ro5pXBt7tsKzJ0Q0 Message-ID: To: Bob Weinand Cc: Nikita Popov , PHP internals Content-Type: text/plain; charset="UTF-8" Subject: Re: [PHP-DEV] [RFC] Typed Properties From: pollita@php.net (Sara Golemon) On Thu, Jun 21, 2018 at 9:13 AM, Bob Weinand wrote: > I agree that we're pretty late to the party, however I see typed properties being > a pretty central feature to the PHP 7.3 feature set then, just because of its size. > I think it may be worth pushing the release of 7.3 a few weeks back instead, > if we decide to have this feature make it into PHP 7.3. > To quote Nikita: https://twitter.com/nikita_ppv/status/1009800042629271553 "Just to make sure we're on the same page: What I mean is that an initial implementation *has* to land before branching, but has a lot of time to bake afterwards. If the implementation is not good enough to land before branching, then it can't go into 7.3." I'm fine with that take on it. If we can get to consensus quickly enough to get a vote closed by the end of July (which, incidentally, allows for a bit past the feature freeze date), then I can get behind it without a additional delay. If we CAN'T close the vote by then, and we're not willing to push the dates out to accommodate, them that's where my 'no' comes from. Last year at this time, a certain new extension rolled right up to the wire and bit beyond and it was a mess. Half the post-branch fixes and API changes didn't even hit the 7.2 branch (without messy cherry-picks) because the committer wasn't paying attention or responding to attempts at communication. Yes, you and Niki are much better plugged in, but other stuff comes up when you leave things for the last minute, and I don't want to see 7.3 have issues as well. -Sara