Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:116835 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 94806 invoked from network); 6 Jan 2022 16:52:50 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 6 Jan 2022 16:52:50 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id EFE69180542 for ; Thu, 6 Jan 2022 10:00:34 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: * X-Spam-Status: No, score=1.6 required=5.0 tests=BAYES_50,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,MISSING_HEADERS, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-wr1-f41.google.com (mail-wr1-f41.google.com [209.85.221.41]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Thu, 6 Jan 2022 10:00:34 -0800 (PST) Received: by mail-wr1-f41.google.com with SMTP id w20so6348727wra.9 for ; Thu, 06 Jan 2022 10:00:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=date:from:cc:subject:user-agent:in-reply-to:references:message-id :mime-version:content-transfer-encoding; bh=nHapqg4lj+daHkEEnu0TMaXLxKl3wrjOrtQTCyCglxQ=; b=V4AIh6ysFASkb88vSsnIoxxAWTRXJ1WGAY2NebttBXBz+bHXofT+qPnWSoQ4qvE/2Z PmE03BVZtcEZZPDNnWJek4g/+tuwygp6DcWoRZdcIDgdOgURAFxoku39GmIbcXLP99Ht AeW90M+AULBlDU6aE9WrAy9cCzm+KAwMneLe6pXqZ2Q5Q36Txri1OIG0YYXvMAdUqkPw IYoyuhwF6NMrh8VhDsJee0yYL4U+SNlvSsOHwdcfF7XWj9RKf9wKd3FPMVBT9BtDq08g zcCtjp/d+IrGA4N1B+AeJC3NOKOIbN8nlHxwsKfKHYGXteDEcBuWADbtD6uVuETiQtV2 /9vg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:cc:subject:user-agent:in-reply-to :references:message-id:mime-version:content-transfer-encoding; bh=nHapqg4lj+daHkEEnu0TMaXLxKl3wrjOrtQTCyCglxQ=; b=Op9Rmz5N58lUOOk2S9psBgpEI1pzvWfnaLjlEKYf3oIWd67GcKxh5PYehRg95EYyuE mV4rZBCrL88t982Qe2XsM5mM52dY4NcHR+sKNt22alQkImzBhYKt1KYH4hdEr24HABFM s4HHTyn7GCqwQ2jOlPBP/XiVrfgltsPateAiMfUQJ4Q/S2ojNc6Gsar6qomUj1ZUNM5a XjwsBo2+Eno1IgHXy0MoRoiDyGGhnFuAmcmAmRt5iNtVURZGMv60kgscpm4ccIW5ckhv bPgTa7Pvi4uQfR6OjK3op2ZGAEidUQecbnFVlRmhLn6RrsudYeDkfwdbq5Gh1vj2cU/Q 7fDA== X-Gm-Message-State: AOAM531hUUK9uq8T7k76w7VvTm3N3rvCgpI7EDIC3hY4+ak88ksBOxGx Q86sw/R8QoIk3IHI6VSlwRxoXn4Py7M= X-Google-Smtp-Source: ABdhPJwmd4R5Vs9hTBzYp9NbL8VjVbR6XXUn+pEwB43n6qdQ7XfnZu03GdvvNZ2Y+PEYqcP/rTMoPQ== X-Received: by 2002:a05:6000:50b:: with SMTP id a11mr20147768wrf.387.1641492033125; Thu, 06 Jan 2022 10:00:33 -0800 (PST) Received: from [127.0.0.1] (cpc104104-brig22-2-0-cust548.3-3.cable.virginm.net. [82.10.58.37]) by smtp.gmail.com with ESMTPSA id u20sm6722778wml.45.2022.01.06.10.00.32 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 06 Jan 2022 10:00:32 -0800 (PST) Date: Thu, 06 Jan 2022 18:00:29 +0000 CC: PHP internals User-Agent: K-9 Mail for Android In-Reply-To: References: <1641335738.195767637@f174.i.mail.ru> <5a4aebf8-e592-4517-8930-d18b112ef1fd@www.fastmail.com> <5a99809d-afda-546c-5a11-a4f0f821aa37@korulczyk.pl> Message-ID: <2164FD98-0348-4477-9D95-30592A362C76@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] RFC: Trait expects interface From: rowan.collins@gmail.com (Rowan Tommins) On 6 January 2022 17:36:41 GMT, "Alexandru P=C4=83tr=C4=83nescu" wrote: >Yes, traits are a language construct that has in general more negative >implications than positive so it's good to keep an eye on their usage=2E >One of the okish usages is to define some implementation for an interface >that classes can use=2E >Limiting that trait to be used only by classes implementing the interface >is seen as a restriction placed on the trait that would not allow it to b= e >used in other places when it might have a negative impact=2E The examples I've generally seen of problematic trait use are more about w= hat's in the trait itself, rather than where it's used=2E I can't really pi= cture what would be the "negative impact" of using somebody else's well-des= igned trait (and if it's not well designed, it presumably wouldn't make use= of the new syntax)=2E Can you give any example scenarios that you think ma= ndating an interface would help avoid? Regards, --=20 Rowan Tommins [IMSoP]