> On Oct 26, 2020, at 10:23 AM, Michał Marcin Brzuchalski
> wrote:
>
> Hi Larry,
>
> I'm wondering why we hadn't thought yet about reducing the need for $this
> in this syntax.
> Since arrow functions have an ability to capture variables defined in
> parent scope why not
> think of the same f
Hi David,
pon., 26 paź 2020 o 15:29 David Rodrigues
napisał(a):
> > The use of > instead of => could if possible indicate the method being
> void
> > and reduce even more:
>
> I think that for void, it could just identify it and not return nothing
> automatically.
>
> function a(): int => b(); /
On 26/10/2020 13:12, Michael Voříšek - ČVUT FEL wrote:
I am writing regarding bug 80248.
Currently, PHP 8 allows parameter reuse at different position, which I
belive is very dangerous, as passed parameters may be passed in a
different order with different object impl.
Hi Michael,
Yes, this w
> The use of > instead of => could if possible indicate the method being
void
> and reduce even more:
I think that for void, it could just identify it and not return nothing
automatically.
function a(): int => b(); // equivalents to function a(): int { return b();
}
function x(): void => y(); //
On 26/10/2020 09:02, Andreas Bittner wrote:
With regards to the JSON looking different when casting to object:
```
json_encode([1,2,3]); // result: [1,2,3]
json_encode((object)[1,2,3]); // result: {"0":1,"1":2,"2":3}
json_encode([]); // result: []
json_encode((object)[]); // result: {}
Than
Hi Larry,
I'm wondering why we hadn't thought yet about reducing the need for $this
in this syntax.
Since arrow functions have an ability to capture variables defined in
parent scope why not
think of the same for class properties which will automatically reduce
short methods verbosity.
class X {
Hi,
I am writing regarding bug 80248.
Currently, PHP 8 allows parameter reuse at different position, which I
belive is very dangerous, as passed parameters may be passed in a
different order with different object impl. See https://3v4l.org/X8omS ,
which is against OOP and LSP.
I belive, we
@Christoph M. Becker
haha that's probably it, i guess that long ago PHP didn't have any
non-crypto hash algos,
one of the results read "256MB Windows 2000"
when was the last time someone rolled a 256MB ram windows 2000?
(am rolling some 128MB ram VPS's, but rolling Windows with such
amounts of ram
On 26.10.2020 at 11:16, Hans Henrik Bergan wrote:
> @Nikita Popov
>
>> How did you draw the conclusion that non-crypto hashes are not included?
>
> yeah i know they're there when you run them, but if you look at the
> benchmarks in the source code, from line 4 - 71, all the non-crypto
> hashes ar
@Nikita Popov
> How did you draw the conclusion that non-crypto hashes are not included?
yeah i know they're there when you run them, but if you look at the
benchmarks in the source code, from line 4 - 71, all the non-crypto
hashes are absent there,
https://github.com/php/php-src/blob/master/ext
Are they? When I run the script, I see things like crc and fnv show up. How
did you draw the conclusion that non-crypto hashes are not included?
Nikita
On Tue, Oct 20, 2020 at 8:20 PM Larry Garfield
wrote:
> A while back, Nikita mentioned that it should now be easy to offer an
> abbreviated syntax for functions that are just a single expression. I
> decided to take a crack at it and it turns out he was right. I thus offer
> this RFC:
>
> https
On Wed, Oct 21, 2020 at 4:59 PM G. P. B. wrote:
> Hello internals,
>
> A rather short RFC about adding support for the "0o" prefix for octal
> integers.
> https://wiki.php.net/rfc/explicit_octal_notation
>
> Surprisingly PHP already accepts the prefix within octdec() and
> base_convert().
>
> I h
I don't follow; is the resulting JSON different if you cast to
object, or is there some other reason you prefer an object over using
an associative array directly?
The by-reference semantics of objects vs arrays in PHP.
*shrug* If you want things to be mutable between functions, stick an & in
14 matches
Mail list logo
