Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:102606 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 93319 invoked from network); 5 Jul 2018 14:43:21 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 5 Jul 2018 14:43:21 -0000 Authentication-Results: pb1.pair.com smtp.mail=j.boggiano@seld.be; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=j.boggiano@seld.be; sender-id=pass Received-SPF: pass (pb1.pair.com: domain seld.be designates 74.125.82.50 as permitted sender) X-PHP-List-Original-Sender: j.boggiano@seld.be X-Host-Fingerprint: 74.125.82.50 mail-wm0-f50.google.com Received: from [74.125.82.50] ([74.125.82.50:36967] helo=mail-wm0-f50.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D0/92-55607-97E2E3B5 for ; Thu, 05 Jul 2018 10:43:21 -0400 Received: by mail-wm0-f50.google.com with SMTP id n17-v6so11393322wmh.2 for ; Thu, 05 Jul 2018 07:43:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=seld-be.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=Z5pn9qeIHhwZF7qc2UeMEedKGUzCEyue+S/sriD4zH0=; b=rDVluoU1S5454NPodAnolniew7/djQAnd4AzmnuOFOuYLJ2KV9bDMDa3/JXPpo0WV7 5ojDejqbLoJgM8aE6pMtyTrwCeDeBwiM0q2oeujwwqCaIBHK82/w6F0E2EXhBeEb/DtE 9C0AGCRbvmYorI+bN4HU2V/r9/Yf+QxxxR5BT7s9xpMYgR1xqBcDfNehiDItRU+C5GLt 8iGXt5Mtf7z2uPqU6dapCNIOuCOvqt+3bSNVZbS7PAjPY/ctpU2Qa0ljMoPhPbohaJUG qY6EtnYeotpUWPfNcI89FisjC2saNBu3uHJm7VR516aHBtZWK4yf0OEHVOWE4ggNb9ON jh8g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=Z5pn9qeIHhwZF7qc2UeMEedKGUzCEyue+S/sriD4zH0=; b=KqWeu5aFfWqFipunfJd/SDxmOsGIVNGNFLfsa1n33+NFgaSBZ6y4Wqp4QY5VPS06sH ba9K6w0ywCFD9hJFQA90Ua5I3tAvsdJXHJfhmqkIAfmwTsYOAWCQbVAO2I2ZaNOmVJVp KGpPpHhD3Vnjsevz0DooYh1SyBVJ9ctqS9sOi+M8k6UwrPCpaLlALtRm4dWH+UdUxhro 6Qe/Mx1U46wIE4KaYqmCtXk/hPav7iJcdiwbK6vLu3t6L/zZx3dwAIYMSWi/zvxJ4U8N fYYdc3nGQIPp4LPJfQhFyabd03J3joTZ1Nrlr8tGu4tMPDV5xlY49mTDrO9LCtrlTf4v I2Kg== X-Gm-Message-State: APt69E2y6vTqy96XdUjXtKafORriLf4hwZr5hA0YeH614BNWk0jXTZXJ Q6cj/b1YtCMFhT6x1GfxZQ/t/79/4wM= X-Google-Smtp-Source: AAOMgpfnHWCodDhcMHPeYFMLn/bLdyQD3inOrhNJMP29o5qPdqOZuE8I6fcEqE/myhMKWrLij3FCHA== X-Received: by 2002:a1c:b208:: with SMTP id b8-v6mr4410757wmf.131.1530801782815; Thu, 05 Jul 2018 07:43:02 -0700 (PDT) Received: from [10.0.8.225] ([178.21.181.98]) by smtp.gmail.com with ESMTPSA id o17-v6sm5782968wrp.62.2018.07.05.07.43.01 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 05 Jul 2018 07:43:01 -0700 (PDT) To: internals@lists.php.net References: Message-ID: <00ee21cb-6a60-ea2d-c805-6ede99ff44b8@seld.be> Date: Thu, 5 Jul 2018 16:43:02 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Subject: Re: [PHP-DEV] Re: [RFC][Vote] iterable_to_array() and iterable_count() From: j.boggiano@seld.be (Jordi Boggiano) Hey, Just to explain the No vote for iterable_count, I think we'd rather advocate people implement Countable in their iterables than to force the consumption of an iterator just to count it as this can have side-effects and render the iterator unusable. If Countable is implemented then count() will do the job and all is well. If consuming the iterator is desired then one still can do count(iterable_to_array($iter)) fairly easily. Best, Jordi On 04/07/2018 00:44, Michael Moravec wrote: > 2018-07-04 0:23 GMT+02:00 Christoph M. Becker : >> Yeah, I'd prefer that. It's not that 2018-07-17 12:00 UTC *couldn't* >> work – it's just I'd rather have some buffer time (I presume there will >> be more RFCs whose voting ends close to feature freeze). > Alright, updated! > RFC voting now closes on 2018-07-16 23:00 UTC. > > M. > -- Jordi Boggiano @seldaek - https://seld.be