On 07/06/2021 21:50, Björn Larsson wrote:
Den 2021-06-02 kl. 22:16, skrev Mike Schinkel:
My only comment/request/suggestion is to consider Mark Randall's
suggestion to use `...?` instead, for the reasons he mentioned in his
email to the list:
https://externals.io/message/114157#114666
On Thu, Jun 10, 2021 at 7:32 PM Guilliam Xavier
wrote:
>
> Since `$null?->whatever(1, 'a')` currently always returns null without
> error, shouldn't `$null?->whatever(?, 'a')` return a closure (with a
> signature built from the placeholders only) that will return null when
> called (i.e.
On Thu, 10 Jun 2021 at 18:32, Guilliam Xavier wrote:
> Since `$null?->whatever(1, 'a')` currently always
> returns null without error, shouldn't `$null?->whatever(?, 'a')` return a
> closure (with a signature built from the placeholders only) that will
> return null when called (i.e. equivalent
On Thu, Jun 10, 2021 at 4:34 PM Larry Garfield
wrote:
> On Thu, Jun 10, 2021, at 3:17 AM, Guilliam Xavier wrote:
> > On Wed, Jun 2, 2021 at 7:47 PM Larry Garfield
> > wrote:
> >
> > > https://wiki.php.net/rfc/partial_function_application
> >
> > for `$null === null`, is `$c = $null->bar(?);` /
Apologies for the subject line. It was a copy-pasta error. All other
messages to other mailing lists have the correct subject.
Cheers,
Ben
signature.asc
Description: OpenPGP digital signature
On Thu, Jun 10, 2021 at 8:40 AM Pierre wrote:
>
> Le 10/06/2021 à 16:16, tyson andre a écrit :
> > So I'm probably changing this to `ImmutableTraversable` as a short name for
> > the functionality,
> > to make it clear arguments are eagerly evaluated when it is created.
> > (ImmutableSequence
Le jeu. 10 juin 2021 à 17:46, Ben Ramsey a écrit :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> PHP 8.1.0alpha1 has just been released and can be downloaded from:
> https://downloads.php.net/~patrickallaert
> Or use the git tag: php-8.1.0alpha1
>
> Windows binaries are available at:
On Thu, Jun 10, 2021 at 7:14 AM Nikita Popov wrote:
>
> On Tue, May 25, 2021 at 4:18 PM Nikita Popov wrote:
>
> > Hi internals,
> >
> > Currently, argument unpacking (...$foo) cannot be combined with named
> > arguments (foo: $bar) at all. Both func(...$args, x: $y) and func(x: $y,
> > ...$args)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
PHP 8.1.0alpha1 has just been released and can be downloaded from:
https://downloads.php.net/~patrickallaert
Or use the git tag: php-8.1.0alpha1
Windows binaries are available at: https://windows.php.net/qa/
This is the first official release of
On Thu, Jun 10, 2021, at 8:14 AM, Nikita Popov wrote:
> On Tue, May 25, 2021 at 4:18 PM Nikita Popov wrote:
>
> > Hi internals,
> >
> > Currently, argument unpacking (...$foo) cannot be combined with named
> > arguments (foo: $bar) at all. Both func(...$args, x: $y) and func(x: $y,
> > ...$args)
Le 10/06/2021 à 16:16, tyson andre a écrit :
So I'm probably changing this to `ImmutableTraversable` as a short name for the
functionality,
to make it clear arguments are eagerly evaluated when it is created.
(ImmutableSequence may be expected to only contain values, and would be
confused with
On Thu, Jun 10, 2021, at 3:17 AM, Guilliam Xavier wrote:
> On Wed, Jun 2, 2021 at 7:47 PM Larry Garfield
> wrote:
>
> > Hi folks. After much off-list discussion, iteration, and consideration,
> > we have a new draft of PFA ready for review.
> >
> > The URL is the same:
> >
> >
Hi Alex,
> > I've created a new RFC https://wiki.php.net/rfc/cachediterable adding
> > CachedIterable,
> > which eagerly evaluates any iterable and contains an immutable copy of the
> > keys and values of the iterable it was constructed from
> >
> > A heads up - I will probably start voting on
On Tue, May 11, 2021 at 10:52 AM Nikita Popov wrote:
> Hi internals,
>
> I'd like to propose the depreciation of the ticks mechanism:
> https://wiki.php.net/rfc/deprecate_ticks
>
> I'm submitting this separately from the PHP 8.1 deprecations RFC, as this
> is a language change, even if not a
On Tue, May 25, 2021 at 4:18 PM Nikita Popov wrote:
> Hi internals,
>
> Currently, argument unpacking (...$foo) cannot be combined with named
> arguments (foo: $bar) at all. Both func(...$args, x: $y) and func(x: $y,
> ...$args) are rejected by the compiler.
>
>
On Thu, Jun 10, 2021, 2:32 PM Nikita Popov wrote:
I'm not sure where you got the strange idea that "readonly" can refer to
> asymmetric visibility. The two syntactic approaches to asymmetric
> visibility that I'm aware of are "{ get; private set; }" in C# and "public
> private(set)" in Swift.
On Wed, Jun 2, 2021 at 7:47 PM Larry Garfield
wrote:
> Hi folks. After much off-list discussion, iteration, and consideration,
> we have a new draft of PFA ready for review.
>
> The URL is the same:
>
> https://wiki.php.net/rfc/partial_function_application
>
Hi, thanks all for the reworks! I
On Thu, Jun 10, 2021 at 3:21 AM Pierre Joye wrote:
> Good morning Larry,
>
> Thank you. Very good summary, maybe worth adding to the RFC :)
>
> On Wed, Jun 9, 2021 at 11:52 PM Larry Garfield
> wrote:
>
> > readonly would be a separate, independent feature/syntax.
>
> Yes, my thought is about
On Thu, Jun 10, 2021 at 11:08 AM Mike Schinkel wrote:
>
> Hi Larry,
>
> Thanks for the response.
>
> > On Jun 9, 2021, at 12:51 PM, Larry Garfield
wrote:
> >
> > Pierre and Mike:
> >
> > "Asymmetric visibility" as we keep referring to it would mean the
"implicit accessors only" version of this:
19 matches
Mail list logo
