Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:108478 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 27519 invoked from network); 11 Feb 2020 14:59:45 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 11 Feb 2020 14:59:45 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id F3CCD180539 for ; Tue, 11 Feb 2020 05:13:40 -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=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM, 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-lj1-f194.google.com (mail-lj1-f194.google.com [209.85.208.194]) (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 ; Tue, 11 Feb 2020 05:13:40 -0800 (PST) Received: by mail-lj1-f194.google.com with SMTP id v17so11520140ljg.4 for ; Tue, 11 Feb 2020 05:13:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=J38UNbuQTOBqeP5JndKnQ4p1Esj+QJ3H4w1z/YDvlyg=; b=CUaA12t7KWwSamBk75Ju/OapgTXSuDTldMDFqjQYBNFlmEb1ycCXWQcgh6kMfrbjYC K8cIBm3p1PDp3iCT3RC23C1seS5darH2E28kZVRl33+7tmUpNDsQ9cQKLIbdO7iAaLwD dVg07rA7jmHdg4c72mfsMoH6DY8bgrubwixnKjHUu8QiDFWwGeqNhnnEZeUy+oORdHBP p5nQCDuRrDVL+p0c9eQ7zGLI1O4jQiFOy8Ee/bI95nIXfVaR5ARqgtXnn3cYRfekvYph BRGXIwHlkvZbIcKgmebkN1gGd5wS10eVSnh+TEqoTEPA4axOwCpaYLWSjsrVPsG0LL8V uSZw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=J38UNbuQTOBqeP5JndKnQ4p1Esj+QJ3H4w1z/YDvlyg=; b=ZKgbpEjNKIu9TAzxttZSRQVBwh+cHRxZIounxyFdo6ghIyxY96gQUGbGC2FHr//aG1 X8ntXetNlf7yfqT0HbIQiL2+cA0GRwvoiSybJI+B1n+mTAoZZ0/jH6pAthuwq3x2tB8w 1sqtaFfRSWixDxli6YmZ1fM0uMhFlVx6E8Z2PHAKOfGvQ5sj6USjmmRM+KGqwDi6JTf1 2Ib3OKZoj80g68iVAFlQ0RuvNyxDTFMObb2mkW9uSmioPSKAEkinYRBVB6xG2+gKJyC/ 80E5L8uV+oYhuOIqUeSFBqBja+3xc7xk6FzZwy+HIaY9S4u0CecUo+8OgESfogcR5KgN nEKw== X-Gm-Message-State: APjAAAUyEdhUZcUtD/hVSJ/arwWkf7Og8P2nozfD7zk+KEqofr8Sk6mD n5+2OZRZd12GPIXlVTCDqDFZeQ70sijfphBm2g== X-Google-Smtp-Source: APXvYqzIlFzhEes4xefNmnplm7oCaCX0s3TngbQCRi0+qiUiEwGWG8JwB6qX2Nd8RAuKJ059wEwJ8iAhQyTeabav55Y= X-Received: by 2002:a2e:9a93:: with SMTP id p19mr4285199lji.177.1581426819120; Tue, 11 Feb 2020 05:13:39 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: Date: Tue, 11 Feb 2020 14:13:27 +0100 Message-ID: To: =?UTF-8?Q?Micha=C5=82_Brzuchalski?= Cc: Nicolas Grekas , Nikita Popov , PHP Internals List Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] [RFC] Adding a "Stringable" interface to PHP 8 From: guilliam.xavier@gmail.com (Guilliam Xavier) On Tue, Feb 11, 2020 at 2:11 PM Micha=C5=82 Brzuchalski wrote: > > wt., 11 lut 2020 o 13:59 Guilliam Xavier napi= sa=C5=82(a): >> >> On Tue, Feb 11, 2020 at 1:12 PM Nicolas Grekas >> wrote: >> > >> > > >> > > Just so someone has mentioned it... is "Stringable" really the best = name >> > > for this interface? Reddit really didn't like it ;) Some possible >> > > alternatives: ToString, HasToString, CastsToString. >> > > >> > >> > Naming things... >> > I'm not sure reddit is the way to lobby php-internals... >> > I proposed Stringable because it is the most consistent to me: >> > Traversable, Serializable, Countable, Throwable, JsonSerializable >> > all are related to some special engine behavior, which this ones also = is. >> >> But one could argue that "string" is not a verb like "traverse", >> "serialize", "count", "throw" etc. >> Potential alternatives would be Stringifyable (or Stringifiable?), >> StringCastable, StringConvertible... >> (Even though I personally have no problem with "Stringable") >> > > Maybe StringObject? We do already have ArrayObject. But ArrayObject is not a interface (ArrayAccess is). --=20 Guilliam Xavier