Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:117982 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 42507 invoked from network); 17 Jun 2022 14:05:52 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 17 Jun 2022 14:05:52 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 1B662180543 for ; Fri, 17 Jun 2022 08:54:08 -0700 (PDT) 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,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS24940 176.9.0.0/16 X-Spam-Virus: No X-Envelope-From: Received: from chrono.xqk7.com (chrono.xqk7.com [176.9.45.72]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Fri, 17 Jun 2022 08:54:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bastelstu.be; s=mail20171119; t=1655481246; bh=FNxizzjCOn619bY7loSLqGciO96G2RHz9NSHSCe43U8=; h=Date:Subject:To:References:From:In-Reply-To:From; b=We30KOdaqtvO0zmPAbxB36MoB0bbRbFLOAnkSrzlfQ0T3gjiujBtqtSVbe4C3laUT 4O23W0wJ7+E+x16i2ExZUJ1J6ed8jpLtsy/5eD5DfJgLpPDFmOFSnwGR+fh51TP26c ls6tFi8v419gDa/NTGcuahKZeqc9LW9ABIno2NlmcHQPq7GUdPEOxQ4jILGpiFzUDV pel7G3DUUlRsY/uCi41B3fZ1xlnqvfN3sDpVLaJFcEVe8H851HwqBoJTcq6IlCLPZB aN50nUKZYjRsEUgHNAn55a5qEq6ipxdAZINQbWnm8I2/eefIws68gDcVFPh+HqtDLN VH9NgoJSnn3HA== Message-ID: <97667f03-2cd6-eeb6-2db0-00953af80f23@bastelstu.be> Date: Fri, 17 Jun 2022 17:54:05 +0200 MIME-Version: 1.0 Content-Language: en-US To: Go Kudo , internals@lists.php.net References: <1717d744-b7df-b39d-f280-83283c11ec7b@bastelstu.be> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] Re: [RFC] [VOTE] Random Extension 5.x From: tim@bastelstu.be (=?UTF-8?Q?Tim_D=c3=bcsterhus?=) Hi On 6/17/22 14:52, Go Kudo wrote: > (3) This is a very tricky problem. As you point out, it took me a while to > figure out PCG64 too. > However, after statistical testing PCG64 (pcg_oneseq-128-xsl-rr-64) seems > to do a good job. > (Though Xoshiro256** does as well, and has a more obvious name.) > > Regarding the naming issue, I have looked at implementations in other > languages > (Python's NumPy and Rust) and none of them seem to be very clear. > > I agree with you about keeping the names clear. Although it is complicated, > I don't think anyone would be particularly bothered by the name > PcgOneseq128XslRr64. > However, some people may continue to use MT because they don't understand > it well. > > I think the possible options are as follows > > A. Rename PCG64 to PcgOneseq128XslRr64 > B. Rename PCG64 to PcgOneseq128XslRr64 and then re-implement the more > obvious Xoshiro256StarStar > C. Remove PCG64 and re-implement Xoshiro256StarStart > > Personally, I think B is the best. > > What do you think? > Any of those would be fine for me. You can either make a decision as the RFC author and include that into a general vote, or you could split this into separate votes (each with a 2/3 decision): - Add xoshiro256** as Xoshiro256StarStar? - If xoshiro256** is added: Remove PCG64? - If PCG64 stays: Rename PCG64 to PcgOneseq128XslRr64? Best regards Tim Düsterhus PS: I believe you missed my suggestion (4) Randomizer::randomString($charset, $length).