Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:93994 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 4984 invoked from network); 15 Jun 2016 09:50:59 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Jun 2016 09:50:59 -0000 Authentication-Results: pb1.pair.com smtp.mail=rowan.collins@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=rowan.collins@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.53 as permitted sender) X-PHP-List-Original-Sender: rowan.collins@gmail.com X-Host-Fingerprint: 74.125.82.53 mail-wm0-f53.google.com Received: from [74.125.82.53] ([74.125.82.53:38503] helo=mail-wm0-f53.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E3/7B-27860-20521675 for ; Wed, 15 Jun 2016 05:50:58 -0400 Received: by mail-wm0-f53.google.com with SMTP id m124so27669492wme.1 for ; Wed, 15 Jun 2016 02:50:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=RohN8qT2rjBMgpKosh+12hmktM0f6fLhzYf1ZP9U2u4=; b=MZMM+fmstaAC4DocrGrdUzJy+43lLC4E73/XsBYXK927IXGnezB3WTWBKsDBRf8Fm+ 2/dwdgpz8joUczTwT/sZ1qEXALYWcI9wZq/C4zRntuAnIGBbClnQ/90YcAP3rQdTvevq bNak/rXyIUpznKqB6h2fsqYr6NIfh6nWGnTk4hdAwcUCdy3VGkBXueKKAajllnvmVJC9 SKbB+B18PQxkHjY4/t+9ZvpJTG92kelrk2cXVEkji1bljpIvGKBLgErJQAGK0FUHxqJR cTZmuk1FAWqKPm/5DHmZIe4p/YqmqBjpGvZXd5HUKq2hoPAqp5N2Q9306s52AaJrMyEL tm4Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=RohN8qT2rjBMgpKosh+12hmktM0f6fLhzYf1ZP9U2u4=; b=J6K3ZpP5xiEYFSeqZ89cRaXgCzS7+Ju/KMbsTSIpe3ulcUtGQchWIp42j0J5E3N16l 5H9Fi0R9c8a7k/ODLrNjXMRKTgtf0eCr7Tj0z9IBE3HFszd6YTTbTjs0cQ0Nv3iGac80 z6ITGfEld/9W+UfggBJP6HSoQlcqNg6jM8NmBKjfwca98gW6QtNALC3Q9NMp9m8eRWyq OrzwwaSyXdr4iahBymMnPv8Ow9F2a4nC8/J7vMVc1H9lWD6lsK9Z2n9Xju32Ec63apWb Sv+7+FaNYK6GuVV2Xzr8M2ooncZlO1G3bN2TGkc8skoy7NSY4/VFhRKIrTOES6Dsm085 uvQQ== X-Gm-Message-State: ALyK8tLsl5BHHas46J8Ry/30BxV9qg9rA9FeVEdmxJaZUdXEHUTxXC0nA+de8hMT3WZT3A== X-Received: by 10.28.94.12 with SMTP id s12mr9442517wmb.54.1465984254955; Wed, 15 Jun 2016 02:50:54 -0700 (PDT) Received: from [192.168.0.98] ([93.188.182.58]) by smtp.gmail.com with ESMTPSA id o2sm10910292wjp.26.2016.06.15.02.50.54 for (version=TLSv1/SSLv3 cipher=OTHER); Wed, 15 Jun 2016 02:50:54 -0700 (PDT) To: internals@lists.php.net References: Message-ID: Date: Wed, 15 Jun 2016 10:48:27 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] How to indicate support for unimplemented part of an RFC From: rowan.collins@gmail.com (Rowan Collins) On 14/06/2016 20:11, Leigh wrote: > 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 :) > In this particular instance, it may be more to the point to create an *implementation* of it. The reason it was omitted was not for lack of desire, but due to practical problems of how to make it work. See for instance http://marc.info/?l=php-internals&m=142791636808421&w=2 Regards, -- Rowan Collins [IMSoP]