Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:93971 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 36691 invoked from network); 14 Jun 2016 19:11:26 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 Jun 2016 19:11:26 -0000 Authentication-Results: pb1.pair.com header.from=leight@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=leight@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.51 as permitted sender) X-PHP-List-Original-Sender: leight@gmail.com X-Host-Fingerprint: 209.85.215.51 mail-lf0-f51.google.com Received: from [209.85.215.51] ([209.85.215.51:36082] helo=mail-lf0-f51.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 74/C1-27860-ED650675 for ; Tue, 14 Jun 2016 15:11:26 -0400 Received: by mail-lf0-f51.google.com with SMTP id q132so72785777lfe.3 for ; Tue, 14 Jun 2016 12:11:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=7gIX2p9EeU0UIz/RTWA0HNb6uEKt00THcOs6k8yKOms=; b=E/t1P83HVf2rhDeBc0pQpWrDAv5AWNpIrA7RCP1uVBHJ84f+TTeWNLUHpejSr2q+du IJrpow5gOpmAD16Em8bSjn67ps+e4DzgpoISrl1TTVDu1EbD9WyO0MU8wQli5LO9wV7o sbm3r1PMoxXPfsWLEqaUz1fjSm8jMV9hkN9nQf9XhgTHZhe7gGee6eMfWQdAD+ZxUYGI CJ0VrKqFLnTOr5dQejpNqhFfklXUJenFrDF0b8ViySkWngKJkP+Bh+q2kEyGY7O+iIF8 awNGVqqP0+UwCkKN7T5KCHLeQ/pboX0jml4qdmG8u+7yaY5UjUo3MGBucjC9fzcDLW0G fDAg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=7gIX2p9EeU0UIz/RTWA0HNb6uEKt00THcOs6k8yKOms=; b=XVaZnXC2bddpADAH1eB8rVt18iQM1iDgxhPtvY/RE0nqRXy5kMNU1aWoYPteDuaB8l vzMtnFeUVfyfpBKTc9taXfTekWwOkGtFQG11WjiMZZZntfaUwXdd1uiDdN+8FCUc7YgY hZEhW4q1n2r7oEH8Ma9VshAE8uPpeyof+vsY4OxTdA0IcuLZp4nTW9r5g5PSkO8wPnEj QUNUdtFOWC74zPxRTnO0Byi8d8Rdbgfry3/DNH73zQFz9eLjoon5ij2SiVClLyCS0CEm FIVP7/RKE7N3HPt44SKt+Vjhd0h0t9fAz/6RXwyjaATDDi8li26b4IcC1NzamwQrsYkZ cBqQ== X-Gm-Message-State: ALyK8tLuk05IFcCyT1zxubZTjA7Y5DY0FB8oGS7qWYTndm/ioph2wCB7AUk7u3IXg9C+yPGUGbJcGrUkEx0qCA== X-Received: by 10.25.148.77 with SMTP id w74mr1894181lfd.2.1465931483405; Tue, 14 Jun 2016 12:11:23 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Tue, 14 Jun 2016 19:11:13 +0000 Message-ID: To: Matthew Browne , internals@lists.php.net Content-Type: multipart/alternative; boundary=001a11401668556206053541c542 Subject: Re: [PHP-DEV] How to indicate support for unimplemented part of an RFC From: leight@gmail.com (Leigh) --001a11401668556206053541c542 Content-Type: text/plain; charset=UTF-8 On Mon, 13 Jun 2016 at 22:30 Matthew Browne wrote: > Hi, > What is the proper way to express support for an item that's not an > official part of an RFC but is listed as an idea for future > consideration? Specifically I wanted to give my "+1" for covariant > return types which are mentioned in passing in this RFC: > https://wiki.php.net/rfc/return_types. I think you'd go ahead and create an RFC for it :) --001a11401668556206053541c542--