Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:94639
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.181 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1469202307.3729097.673942625.3A62CE90@webmail.messagingengine.com>
References: <CAEsg9X3N_DT=tXr3gJtxtkk+=cnvp0o0WEz2fw8eCEJ0uPO14Q@mail.gmail.com>
 <1469202307.3729097.673942625.3A62CE90@webmail.messagingengine.com>
Date: Fri, 22 Jul 2016 16:00:20 -0300
Message-ID: <CAEsg9X2wr=3iozrhS9sXN-UmbJqYFX8HKbKK4RbDLrz89Nr3xg@mail.gmail.com>
To: Larry Garfield <larry@garfieldtech.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] RFC: lazy statements
From: david.proweb@gmail.com (David Rodrigues)

> However, that also means there's an enormous potential for race
> conditions.  Technically no more than closures now, but the use cases
> seem like they'd make it more prevalent.  If you "use" by reference, or
> use a mutable object, or a service that depends on IO, etc. then the
> resulting value of the lazy variable is not technically
> non-deterministic, but will certainly feel like it to the developer.

I think that lazy statements should not be used when you can have
possibilities like that. It should not be a substitute to methods.

So, for instance, if I have a mutable dependency, is better I create
a method to do that, that could work better with that.

I can think about how we can handle this, but I need a real case
where this problem can exists. Can you help with this?

Thanks!