Nikita Popov

Not sure I understand how you want to handle this on 32-bit. If you want to drop the Token object entirely (rather than just reduce the number of properties on...

__get and __set are *very* slow. From a quick check on 7.1 __get is ~5x slower than a declared property lookup and ~2.5x slower than a normal method call. On...

> why is it that __get and __set introduce the same memory overhead as a property, unlike normal methods? Magic getters have per-property recursion guards, which means that if you're...

As to native extensions: For this type of extension (no interaction with engine internals) the API should be *relatively* stable for 7.x. If there will be breaking changes, they will...

I think we need an FCP for this one, given the public-facing change -- could someone from the compiler team start one? (Or would it be preferred to do that...

Sounds good

@remicollet I added some more notes to the changelog. And yes, please create the PECL release, I haven't done one in ages...

What SAPI are you using? The APCu cache is per-process on Windows, so if you are using a process-based (rather than thread-based) SAPI, then it will not be shared between...

Reduced example: ```llvm target datalayout = "e-m:e-p270:32:32-p271:32:32-p272:64:64-i64:64-f80:128-n8:16:32:64-S128" target triple = "x86_64-unknown-linux-gnu" define i64 @test(ptr %arr) { entry: br label %loop loop: %accum = phi i64 [ %accum.next, %loop ], [...

Upstream issue: https://github.com/llvm/llvm-project/issues/57476 Alternatively, this would also be fixed if we managed to unroll the loop early (during full unroll rather than runtime unroll). That's probably where the into_iter distinction...