Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:113928 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 33621 invoked from network); 2 Apr 2021 03:48:12 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 2 Apr 2021 03:48:12 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 1265D1804B7 for ; Thu, 1 Apr 2021 20:46: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,FREEMAIL_FROM,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from mail-lj1-f169.google.com (mail-lj1-f169.google.com [209.85.208.169]) (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, 1 Apr 2021 20:46:07 -0700 (PDT) Received: by mail-lj1-f169.google.com with SMTP id c6so2909637lji.8 for ; Thu, 01 Apr 2021 20:46:07 -0700 (PDT) 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; bh=mBddgpMQCUBt1nqo8DHAwtgGKXPunrUe/n+MOI0qMIU=; b=PZe/9+UxTNTA6kR6xcwhmmaqPmiyUpQaWEN6MVX93l+mQ1q+0XImk+qNbVZevIbjhs vH85tzaa6G3QkQhlsevP054HjLspl1jE2lOx6tAMxyoFPpOpoWQc8FHzFUeYk574cYIn BIoVaxRO1fnCKruo1Mev2qWi0U/20oKq3J3bNluoir/4+wReUBJd5oKQp3mThuohKyLX XvBon3UwrNJPOH30b/EFPjNHifkscHGeORu/R6KuUhYEYim8RckdbuEXJcLeNHeviXtw yJye++J7UzRNF2wYQQYO/M1LdNrNnY/YDnSQgJxy9DGStSsg7dvsybWx3g/hQMehuXAD a6CQ== 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; bh=mBddgpMQCUBt1nqo8DHAwtgGKXPunrUe/n+MOI0qMIU=; b=P+JoPVSAR9/wIruxOzF0JVC7f9U4E6jXtadAIvp1+fCpuJaSFtd/itdDF4rNAJTkBt L+fIspUqtn9GMcaXpw7pY6+PBLg+qdsaT/BtWPZeAv3JCOUW0jCtNVRCIViDGN30rR0H dA8tgF4Q9zN5G1bmJyNbjlE31faySULKUGBYHhKyn939O7UajM3O3VVCKIKFinmtir6i /MUTLCscEDxgZCfCgvrJB98K5TYJS48wmdSm+nPgfV/CCRFbAB5UiNakd+G7nIrkTfSF qujb9THwfPFWrZW34REGtaKiGHpSU11SSAnBJUzjQnnLzn9xpyRtOf12xkNa2m4hk9dM 0eRQ== X-Gm-Message-State: AOAM533F6q7f4Re87cGL6wFq5cwFWsJq4bMDpP0ft90uhRGZSH+zaJ8l Q9/EW0ESD+fUd8uKao3NGPD58W1EUgKRT+bnzfa9eQi3uno= X-Google-Smtp-Source: ABdhPJwYZ1p9VvTe4M+IrWsBzq8ldXbMFZuQtCP4NUCTQorMImkoBwd3PEYoFf2yvyJl9qqWH+kOxQygmwA5eH9Td24= X-Received: by 2002:a2e:5804:: with SMTP id m4mr7144991ljb.419.1617335162607; Thu, 01 Apr 2021 20:46:02 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Fri, 2 Apr 2021 12:45:51 +0900 Message-ID: To: Levi Morrison , PHP internals Content-Type: multipart/alternative; boundary="000000000000d99b9305bef52fcd" Subject: Re: [PHP-DEV] [VOTE] Object scoped RNG implementation From: zeriyoshi@gmail.com (Go Kudo) --000000000000d99b9305bef52fcd Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Morrison. > Sorry if I missed an optional "intent to vote soon" thread. I thought I had announced it here, but I did not indicate the specific dates. I apologize for that. https://externals.io/message/113720 > simply based on the fact that namespaced things are going into`ext/standard`. Yes, I feel that the use of namespaces is an area that needs to be carefully discussed. The goal of this RFC is just to get such a feature into core, and we are not particularly concerned about namespaces. (In other words, we think it's fine to change RNG\RNGInterface to RNGInterface and RNG\XorShift128Plus to XorShift128PlusRNG and not use namespaces.) As per the RFC, we believe this feature is necessary for approaches like Fiber and Swoole, which have more complex execution order and state management. What if you have a problem with this feature being implemented in `ext/standard`? I think this is unavoidable since `shuffle()`, `array_rand()`, and `str_suffle()` are implemented in `ext/standard`. The original RFC suggested quarantining them as `ext/rng` to avoid this (PECL orng is mostly based on the original idea), but the global state dependent `shuffle()`, `array_rand()`, and `str_shuffle()` are implemented in `ext/standard`. ext/standard` are implemented and not deprecated, the possibility of unintentionally writing state-dependent code increases in the future. Let me know what you think. 2021=E5=B9=B44=E6=9C=882=E6=97=A5(=E9=87=91) 4:19 Levi Morrison : > On Wed, Mar 31, 2021 at 10:39 PM Go Kudo wrote: > > > > Hello everyone. > > > > Object scoped RNG RFC vote is now open. > > https://wiki.php.net/rfc/object_scope_prng > > > > The deadline for voting is April 15. > > > > Previous discussions can be viewed below. > > > > https://externals.io/message/112765 > > https://externals.io/message/112819 > > https://externals.io/message/113720 > > > > Regards, > > Go Kudo > > Sorry if I missed an optional "intent to vote soon" thread. I voted no > simply based on the fact that namespaced things are going into > `ext/standard`. We have an open RFC discussion on this issue, which > has had discussion as recently as 10 days ago. I cannot vote "yes" on > anything involved with namespaces in this context in good conscience. > > At the same time, we shouldn't block things indefinitely. > --000000000000d99b9305bef52fcd--