On Fri, Aug 8, 2025, at 07:57, Mihail Liahimov wrote:
> Yeah, it seems to be problematic to use this syntax with finally blocks.
> Perhaps the optional catch block should be allowed only at the very end, but
> it sounds somehow doubtful.
>
> ср, 6 авг. 2025 г. в 16:52, Andreas Heigl :
>> Hey Mih
Yeah, it seems to be problematic to use this syntax with finally blocks.
Perhaps the optional catch block should be allowed only at the very end,
but it sounds somehow doubtful.
ср, 6 авг. 2025 г. в 16:52, Andreas Heigl :
> Hey Mihail
>
> Am 06.08.25 um 13:34 schrieb Mihail Liahimov:
> > Hi!
> >
On Thu, Jul 24, 2025 at 2:06 PM Daniel Scherzer
wrote:
> Hi internals,
>
> Voting is now open for this RFC.
>
> * RFC: https://wiki.php.net/rfc/deprecated_traits
> * Discussion thread: https://externals.io/message/127912
>
> Voting will end 2025-08-07 at end-of-day UTC.
>
> -Daniel
>
I have clos
On Thu, Jul 24, 2025 at 2:05 PM Daniel Scherzer
wrote:
> Hi internals,
>
> Voting is now open for this RFC.
>
> * RFC: https://wiki.php.net/rfc/filter_throw_on_failure
> * Discussion thread: https://externals.io/message/127911
>
> Voting will end 2025-08-07 at end-of-day UTC.
>
> -Daniel
>
I hav
On 2025-08-08 10:01, Rob Landers wrote:
For example, if |A::foo(): int| promises to always return a non-zero
integer, and a subclass overrides |foo()| to only return zero, that
violates the contract—even though the type signatures match perfectly.
This is the sort of semantic guarantee that
On Thu, Aug 7, 2025, at 20:37, Jonathan Vollebregt wrote:
> On 8/7/25 12:38 AM, Hans Krentel wrote:
> > > > From a child class's perspective, the "public interface" is both
> > protected + public of the parent. If you change or misuse a parent's
> > implementation or invariants, it violates LS
On 8/7/25 12:38 AM, Hans Krentel wrote:
> > From a child class's perspective, the "public interface" is both
protected + public of the parent. If you change or misuse a parent's
implementation or invariants, it violates LSP, even if it doesn't affect
external clients immediately.
Ah okay, th
Hi Vinicius,
as Ilija mentioned you can see here an overall view on the current 55%
line coverage in PHP. I guess its "line coverage" (a less strong code
coverage type in comparison to types like "branch coverage", "MC/DC" or
wonderful "path coverage"):
https://app.codecov.io/github/php/php-s
Hi Vinicius
On Thu, Aug 7, 2025 at 5:20 PM Vinicius Dias wrote:
>
> I would like to know how or where I can find the code coverage for
> php-src to see if there is any uncovered code I might be able to
> contribute with new tests.
It lives here:
https://app.codecov.io/github/php/php-src
Howeve
On Thursday 07 August 2025 08:46:26 (+02:00), Rob Landers wrote:
>
>
> On Thu, Aug 7, 2025, at 00:38, Hans Krentel wrote:
> >
> >
> >
> > On Wednesday 06 August 2025 13:41:14 (+02:00), Rob Landers wrote:
> >
> > >
> > >
> > > On Wed, Aug 6, 2025, at 13:26, Hans Krentel wrote:
> > > >
On Friday 04 July 2025 14:40:23 (+02:00), Tim Düsterhus wrote:
> Hi
>
> On 7/3/25 18:04, Derick Rethans wrote:
> > The intention behind the filter extension was that admins can set a
> > default filter for *all* data coming in through this `filter.default`
> > setting as a "safe" fallback. Th
Hi,
As part of moving all servers to a new infrastructure, I have now
prepared the "main" server, which handles wiki auth, notes management,
account management, etc.
I need to transfer the data over, and then update DNS. That's a process
that takes up to 15 minutes (but likely a lot less) in w
12 matches
Mail list logo
