Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:98575
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.48 as permitted sender)
MIME-Version: 1.0
References: <ba9f19e2-813e-d704-75d9-796f9b634ffa@php.net> <CANUQDCjgRw-p9SVVLevhgi4g7FvQOWi0a8G+R5dyoz1sC5nSbA@mail.gmail.com>
In-Reply-To: <CANUQDCjgRw-p9SVVLevhgi4g7FvQOWi0a8G+R5dyoz1sC5nSbA@mail.gmail.com>
Date: Fri, 17 Mar 2017 12:57:20 +0000
Message-ID: <CADxrgCPBJgGgqfdv_dpw+4_-iW_XK=2ziCLXjSqxiChvuimLmw@mail.gmail.com>
To: Niklas Keller <me@kelunik.com>, PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=94eb2c088fb87978f0054aecb896
Subject: Re: [PHP-DEV] Let range() return a generator?
From: adambaratz@php.net (Adam Baratz)

--94eb2c088fb87978f0054aecb896
Content-Type: text/plain; charset=UTF-8

> Yes, that's a BC break. Instead of changing it, there could be a new
> function. But as it can be simply built in userland, I don't see much
> reason to have it in core.


Whether or not it's in core, the two-pronged approach is what Python does
(range and xrange). Sometimes you want an array and not a generator. That
language is really sympathetic to generator use, but it never forces you to
use them. The core libraries are structured thoughtfully in that regard.

Thanks,
Adam

--94eb2c088fb87978f0054aecb896--