ld be achieved simply by creating a single repository under the php
organization on GitHub. What are your thoughts on this?
Best Regards.
Go Kudo
2024年9月3日(火) 10:35 Ben Ramsey :
> > On Sep 2, 2024, at 19:36, Bob Weinand wrote:
> >
> > On 3.9.2024 02:18:30, Ben Ramsey wrote:
> >>> On Sep 2, 2024, at 18:53, Bob Weinand wrote:
> >>>
> >>> On 3.9.2024 01:44:21, Ben Ramsey wrote:
with the php image on DockerHub.
Best regards,
Go Kudo
uble of switching and
be very helpful.
Best regards,
Go Kudo
gt; Regards:
> Máté Kocsis
>
Hi.
I realized I was about to add the deprecation of `lcg_value()` and forgot
to do so, so I added it.
https://wiki.php.net/rfc/deprecations_php_8_3#global_combined_lcg
As usual, my English is of low quality, so I would appreciate it if you
could point out any problems.
Best regards.
Go Kudo
here is no suitable alternative for `lcg_value()`. The
simpler `Randomizer::getFloat()` would be fine, but on the other hand,
floating-point random numbers are very hard to handle, so some say that the
`Randomizer` class should be used. I would like to hear your opinion on
this.
Best Regards,
Go Kudo
2023年5月30日(火) 4:49 Tim Düsterhus :
> Hi
>
> On 5/29/23 08:44, Go Kudo wrote:
> > I realized I was about to add the deprecation of `lcg_value()` and forgot
> > to do so, so I added it.
> >
> > https://wiki.php.net/rfc/deprecations_php_8_3#global_combined_lcg
>
`random_int()` available. This is the only
complete and safe way.
Most of all, while `mt_rand()` is deprecated, we can wait for PHP 9 to
actually remove it from the core. By that time, migration methods using
tools such as Rector will probably have become major. The purpose of the
deprecation is to avoid including it in new codebases that will be written
in the future.
I look forward to your reply.
Best Regards,
Go Kudo
e side, there's no need
for dirty hacks using usleep.
I'd like to hear your opinions. Thank you.
Best Regards,
Go Kudo
2024年7月1日(月) 22:07 Go Kudo :
> Hi, Internals.
>
> I've been absent for a long time due to poor health. I'm finally back.
>
> I maintain a legacy application written in PHP, and occasionally need to
> fake the current time for testing purposes. However, PHP doesn't
aside, I once proposed deprecating the `mt_rand()`, `mt_srand()`,
`rand()`, and `srand()` functions.
However, it was rejected on the grounds that it was unnecessary and
excessive for many workloads. Couldn't the same be said for this case?
https://wiki.php.net/rfc/deprecations_php_8_3
I look forward
gards,
Go Kudo
gt; class RNGUtil {
> public static function shuffleArray(int $randomNumber, array $arr): array;
> public static function randomArrayElement(int $randomNumber, array $arr):
> mixed;
> public static function between(int $randomNumber, int $min = PHP_INT_MIN,
> int $ma
ZTS Thread ID) and time as entropy.
> https://github.com/php/php-src/blob/master/ext/standard/lcg.c#L72
>
> With the development of container technology, this problem seems to be
> getting more serious. So I think we should use the random numbers provided
> by the OS (getrandom on Linux) if available.
>
> I would like to hear your opinions.
>
> Regards
> Go Kudo
>
g the `next64()` method in the interface?
Regards,
Go Kudo
2021年1月5日(火) 23:53 Nikita Popov :
> On Thu, Dec 24, 2020 at 5:12 PM zeriyoshi wrote:
>
>> I updated the RFC draft and changed it to a proposal to bifurcate the
>> interface.
>>
>> https://wiki.php.net/rfc/
ut it is
not smart to say the least.
https://github.com/php/php-src/pull/6568/files#diff-0f1c13e606f11fb5da8dc091109852a6dec328e5aea2389091ff839510cf23faR275
Based on the above discussion, I have added TypeC2 to the RFC.
How about this?
https://wiki.php.net/rfc/object_scope_prng
Regards,
Go Kudo
2021年1月6日(水) 19:50 Nikita Po
Hi internals.
I think I'm ready to discuss this RFC.
https://wiki.php.net/rfc/object_scope_prng
Previous internals thread: https://externals.io/message/112525
Now is the time to let me know what you think.
Regards,
Go Kudo
.
Regards,
Go Kudo
2021年1月9日(土) 19:00 Go Kudo :
> Hi internals.
>
> I think I'm ready to discuss this RFC.
> https://wiki.php.net/rfc/object_scope_prng
>
> Previous internals thread: https://externals.io/message/112525
>
> Now is the time to let me know what you think.
>
> Regards,
> Go Kudo
>
ation, everything is left up to the
implementation.
Personally, I think it would be better to define another interface for the
next64() method that inherits from RNGInterface, what do you think?
Regards,
Go Kudo
2021年1月9日(土) 19:00 Go Kudo :
> Hi internals.
>
> I think I'm ready to discus
MT19937 is redundant. This can be merged.
Anyway, I think the code is finally ready for review.
Once that is done, we will start voting on RFCs.
Regards,
Go Kudo
2021年1月9日(土) 19:00 Go Kudo :
> Hi internals.
>
> I think I'm ready to discuss this RFC.
> https://wiki.php.net/rfc/obje
and()` function with the
RNG\MT19937.
I said I wanted to initiate a vote, but there seems to be too much
discussion missing for that.
I'd like to wait and see for a while.
Regards,
Go Kudo
2021年1月17日(日) 20:02 Go Kudo :
> Updated the RFC and fixed the implementation.
> Also made some ad
Yes. RNG stands for Random Number Generator, which I think is a common
acronym.
Cryptographic pseudo-random number generators are commonly known as a
CSPRNG.
2021年1月19日(火) 1:42 Kamil Tekiela :
> What does rng stand for? Is it short for range or acronym of random number
> generator?
>
pretty "exotic" for a core implementation. :o
Does anyone have any good ideas?
After all this time, I'm not good at English, and I apologize if this is
inappropriate.
Regards,
Go Kudo
2021年1月20日(水) 1:19 Nikita Popov :
> On Mon, Jan 18, 2021 at 5:29 PM Go Kudo wrot
ator`, etc?
We are looking for feedback on these problems.
Regards,
Go Kudo
2021年1月9日(土) 19:00 Go Kudo :
> Hi internals.
>
> I think I'm ready to discuss this RFC.
> https://wiki.php.net/rfc/object_scope_prng
>
> Previous internals thread: https://externals.io/message/11
positively by
externals, but there hasn't been much reaction. I'm unsure when I should
start voting on this RFC.
Regards,
Go Kudo
2021年1月9日(土) 19:00 Go Kudo :
> Hi internals.
>
> I think I'm ready to discuss this RFC.
> https://wiki.php.net/rfc/object_scope_prng
&g
will move forward. Thanks for your input.
Regards,
Go Kudo
2021年1月27日(水) 22:24 Alexandru Pătrănescu :
>
> On Tue, Jan 26, 2021 at 8:06 PM Go Kudo wrote:
>
>> RFCs have been reorganized and radically rewritten.
>> https://wiki.php.net/rfc/object_scope_prng
>>
>&g
le
RFC.
https://wiki.php.net/rfc/object_scope_prng
Perhaps now is the time to discuss this proposal.
I would like to include this implementation in PHP 8.1's Fiber. If there is
no further discussion, I will move on to the voting phase.
Regards,
Go Kudo
,
Go Kudo
I fixed it.
https://wiki.php.net/rfc/object_scope_prng
Thank you.
2021年4月1日(木) 15:23 Max Semenik :
> The "Proposed Voting Choices" section title needs an update.
>
> чт, 1 апр. 2021 г., 07:39 Go Kudo :
>
>> Hello everyone.
>>
>> Object scoped RNG RFC v
Hi Xavier
> If I understand correctly, this would
> - provide us with performant object-encapsulated (isolated from global
state) equivalents of the existing `mt_srand()`/`mt_rand()` and
`random_int()` functions as well as a new "XorShift128+"; along with some
global functions for usability, nota
, `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年4月2日(金) 4:19 Levi Morrison :
> On Wed, Mar 31, 2021 at
ch "error checking" from a userland
implementation, this is the way it is.
This RFC ballot should be rescinded. There was too little discussion
beforehand.
I will create a new proposal based on the feedback I received. I would
appreciate your active input so that this does not happen du
for it?
- What issues do you think should have been resolved between proposal and
ballot in the previous RFC?
I would like a variety of opinions.
Translated with www.DeepL.com/Translator (free version)
Regards,
Go Kudo
mespace.
2021年5月12日(水) 4:46 Levi Morrison :
> On Tue, May 11, 2021 at 6:58 AM Go Kudo wrote:
> >
> > Hi internals.
> >
> > I previously proposed an object scope RNG implementation inside.
> > However, the RFC was rejected after a vote.
> >
> &g
水) 6:21 Larry Garfield :
> On Tue, May 11, 2021, at 7:57 AM, Go Kudo wrote:
> > Hi internals.
> >
> > I previously proposed an object scope RNG implementation inside.
> > However, the RFC was rejected after a vote.
> >
> > https://wiki.php.net/rfc/object_s
Sorry about that. I thought I had indicated that I was getting rid of
bc-break and carving out functionality for the `ext/rng` extension in the
context of reverting to an ORNG-like class-based implementation.
2021年5月12日(水) 23:51 Levi Morrison :
> > Also, I am happy to see that Nikita's rules for
believe that the problem with the previous RFC was that it was just an
ugly API. I propose to sort this out and deprecate the existing functions
that should be replaced.
I would like to ask for feedback on this draft RFC.
Regards,
Go kudo
Keeping old implementations may lead to code being written that
unintentionally relies on the PHPs global state.
Deprecating them reduces the possibility that such code will be written
anew.
2021年5月19日(水) 2:29 Kamil Tekiela :
> Hi Go Kudo,
>
> I think this proposal is much better than the
d left no way
to even maintain backward compatibility.
Compared to that, this proposal is not disruptive in the sense that it
provides a complete alternative.
2021年5月19日(水) 2:43 Rowan Tommins :
> On 18/05/2021 17:19, Go Kudo wrote:
> > I have created a draft of the RFC.
> >
or the detailed remarks. Based on these, I would like to clean up
the RFC.
Regards,
Go Kudo
2021年5月19日(水) 18:46 Guilliam Xavier :
>
>
> On Tue, May 18, 2021 at 6:19 PM Go Kudo wrote:
>
>> Hello internals.
>>
>> I have created a draft of the RFC.
>>
>> h
Thank you. I'm convinced for the most part.
I will probably have to separate this into a separate RFC. I'd like to
remove the existing reference to `mt_rand()` from this RFC, and not include
the BC break.
Regards,
Go Kudo
2021年5月20日(木) 17:46 Rowan Tommins :
> On 20/05/2021 05:59,
from.
I think I've answered all the questions I've been getting on Open Issues.
If I have left anything out, please let me know.
Regards,
Go Kudo
t to
show more details.
Regards,
Go Kudo
2021年5月23日(日) 5:56 Go Kudo :
> Hi, Internals and all participated in the previous discussion.
>
> RFCs have been cleaned up and the proposal has been substantially changed.
>
> https://wiki.php.net/rfc/rng_extension
>
> First of all, I apolog
8PLUS, ?int $seed = null) {}
}
```
2021年5月26日(水) 0:35 Go Kudo :
> Hi, Thanks for the response.
>
> The RFC has been revised based on the points you pointed out.
>
> https://wiki.php.net/rfc/rng_extension
>
> The main changes are as follows:
>
> - Class name has been chan
Hello internals.
Thanks for continuing to participate in the discussion.
I've sorted out the proposal, and finished writing and implementing the RFC.
(Funny, I know.) I think it's time to start a discussion.
https://wiki.php.net/rfc/rng_extension
https://github.com/php/php-src/pull/7079
The main
it is available, then it is certainly more appropriate.
Regards,
Go Kudo
2021年6月2日(水) 17:51 Jordi Boggiano :
> On 01/06/2021 16:28, Go Kudo wrote:
> > Hello internals.
> > Thanks for continuing to participate in the discussion.
> >
> > I've sorted out the proposal, and
vior. However, I don't see
a problem with this behavior.
I feel that the standard PHP behavior is preferable to changing the
userland behavior in a specific way.
I would like to solicit opinions.
Regards,
Go Kudo
2021年6月1日(火) 23:28 Go Kudo :
> Hello internals.
> Thanks for contin
);
var_dump($random->nextInt() === $random_unserialized->nextInt()); // true
```
Regards,
Go Kudo
2021年6月2日(水) 17:51 Jordi Boggiano :
> On 01/06/2021 16:28, Go Kudo wrote:
> > Hello internals.
> > Thanks for continuing to participate in the discussion.
> >
> > I've
e other methods only use 32bit internally.
If you are concerned about this, you should probably be concerned about the
incompatibility with MT_RAND_PHP.
That problem can also be compensated for with an extension that adds algo.
Regards,
Go Kudo
2021年6月9日(水) 19:07 Guilliam Xavier :
> Hello Go
argument, it uses the default, XorShift128+, internally.
Also, whether the Random class is serializable or clonable depends on the
instance of RandomNumberGenerator being used. This means that when the
Random class clone is called, the `$rng` member will be implicitly cloned.
How about this?
Regards,
ntified. From the code, it looks like memory management is being
done properly.
I have a somewhat tricky way of allocating memory to make the process
common, do I need to give some hints to Valgrind?
If you know, I would appreciate your advice on this issue.
Regards,
Go Kudo
be implemented in the future.
> Can you also clarify what happens when serialization or cloning fails?
OK, I've updated it. But these are not special behaviors, they are built on
top of the standard PHP mechanisms.
Regards,
Go Kudo
2021年6月26日(土) 17:55 Kamil Tekiela :
> Hi Go Kudo,
&
the interface Random\NumberGenerator (with implementation in the
sub-namespace), rather than Random\NumberGenerator\RandomNumberGenerator.
Deep-rooted problem. For now, I'm going to change RandomNumberGenerator to
Random\NumberGenerator. It's the best one so far.
I continue to be plagued by Va
rently, there is no way to check this, but we believe that since the RNG
implementation is now class-based, there is no need to check this anymore.
The size of the RNG to be generated is clear at the time of implementation,
and implementing a way to check this would override the method and break
cons
sage/112525
However, the proposal never actually took place. This RFC is a realization
of that proposal.
Is that what you asked?
Regards,
Go Kudo
2021年7月6日(火) 22:46 Remi Collet :
> Le 26/06/2021 à 02:39, Go Kudo a écrit :
> > Hello Internals.
> >
> > RFC has b
>generate() to access the raw RNG stream.
Indeed. I think nextInt() can be removed from Random, since it currently
returns exactly the same value. (However, I think
NumberGenerator::generate() should be kept).
Regards,
Go Kudo
2021年7月6日(火) 23:35 Nikita Popov :
> On Fri, Jul 2, 2021 at 3:
> We can rename the ext/standard header.
OK. I'll rename random in ext/standard. This will not be BC break maybe.
2021年7月7日(水) 19:32 Nikita Popov :
> On Tue, Jul 6, 2021 at 4:38 PM Go Kudo wrote:
>
>> > 1st
>>
>> This is to avoid conflicts with the impleme
...
- standard_random.c ...
Which would be better?
Regards,
Go Kudo
2021年7月7日(水) 19:32 Nikita Popov :
> On Tue, Jul 6, 2021 at 4:38 PM Go Kudo wrote:
>
>> > 1st
>>
>> This is to avoid conflicts with the implementation in ext/standard. I
>> don't
>> want to do it t
We'll do it that way.
Thanks for fixing the memory issue. I'm not quite sure I understand the
principle, so I will investigate.
By the way, are you working on something now? If so, I'll pause the work.
Regards,
Go Kudo
2021年7月7日(水) 21:41 Nikita Popov :
> On Wed, Jul 7, 2021
ll over the
weekend, along with a detailed explanation via email to assist RFC's clumsy
English.
I will make this announcement again, but please let me know if you have any
questions before then.
Regards,
Go Kudo
2021年7月7日(水) 22:10 Nikita Popov :
> On Wed, Jul 7, 2021 at 3:08 PM
php_random_bytes_throw / php_random_bytes_silent macros, this will
result in a BC break.
Are you sure there is no problem doing this?
Translated with www.DeepL.com/Translator (free version)
Regards,
Go Kudo
2021年7月7日(水) 22:10 Nikita Popov :
> On Wed, Jul 7, 2021 at 3:08 PM Go Kudo wr
it published in PECL so that features are
available quickly.
Regards,
Go Kudo
2021年6月26日(土) 9:39 Go Kudo :
> Hello Internals.
>
> RFC has been reorganized for finalization.
>
> https://wiki.php.net/rfc/rng_extension
>
> The changes from the previous version are as follows:
&
responses.
Regards,
Go Kudo
voting the week after next.
Regards,
Go Kudo
2021年9月3日(金) 3:26 Larry Garfield :
> On Thu, Sep 2, 2021, at 10:10 AM, Go Kudo wrote:
> > Hi Internals.
> >
> > Expanded from the previous RFC and changed it to an RFC that organizes
> the
> > whole PHP random number gen
My apologies. I had skipped one.
> And either way it needs more clarity about how you'd write one for reals.
Added a simple example comparing it to mt_rand. What do you think of this?
2021年9月3日(金) 3:26 Larry Garfield :
> On Thu, Sep 2, 2021, at 10:10 AM, Go Kudo wrote:
>
an unsecured random number.
I apologize for the difficulty in conveying this message. I've revised the
wording.
> Changes random source to php_random_int() in shuffle(), str_shuffle(),
and array_rand() .
2021年9月3日(金) 23:04 Larry Garfield :
> On Fri, Sep 3, 2021, at 8:55 AM, Go Ku
m number. I don't see any problem with these
functions using php_random_int() as a random number source.
Regards,
Go Kudo
2021年9月4日(土) 1:02 Nikita Popov :
> On Thu, Sep 2, 2021 at 5:10 PM Go Kudo wrote:
>
>> Hi Internals.
>>
>> Expanded from the previous RFC and changed i
ve. I have
no intention to do so.
Regards,
Go Kudo
2021年9月5日(日) 1:12 Ben Ramsey :
> Go Kudo wrote on 9/2/21 10:10:
> > Hi Internals.
> >
> > Expanded from the previous RFC and changed it to an RFC that organizes
> the
> > whole PHP random number generator.
ssary, but if we
were to try to provide an OOP API without BC Break, what do you think would
be the ideal form?
Regards,
Go Kudo
2021年9月5日(日) 4:24 Dan Ackroyd :
> On Fri, 3 Sept 2021 at 18:41, Go Kudo wrote:
> >
> > Nikita wrote:
> >> this one also moves all of the exist
th a fix for the RNG\NumberGenerator implementation.
Regards,
Go Kudo
2021年9月5日(日) 5:57 Marc :
>
> On 9/2/21 5:10 PM, Go Kudo wrote:
> > Hi Internals.
> >
> > Expanded from the previous RFC and changed it to an RFC that organizes
> the
> > whole PHP random number generator
/random_ext
Hopefully this will get a good response.
Regards,
Go Kudo
andard to ext/random. I would appreciate it if you could check it out.
https://wiki.php.net/rfc/random_ext
Regards,
Go Kudo
2021年9月7日(火) 2:24 Ben Ramsey :
> Nikita Popov wrote on 9/6/21 03:06:
> > On Sun, Sep 5, 2021 at 7:40 PM Ben Ramsey wrote:
> >
> >> Go Kudo wrote on
t for a more SIMD friendly RNG.
Regards,
Go Kudo
2021年9月7日(火) 17:28 Nikita Popov :
> On Thu, Sep 2, 2021 at 5:10 PM Go Kudo wrote:
>
>> Hi Internals.
>>
>> Expanded from the previous RFC and changed it to an RFC that organizes the
>> whole PHP random number generator
The voting phase for the following RFCs will begin as soon as two weeks
have passed.
https://externals.io/message/115975
I don't see any particular discussion, so I'm contacting you just in case.
Best regards.
Go Kudo
I had misunderstood this for a long time. Now I understand.
This is certainly something to think about.
However, I think we also need to consider compatibility. How about
something like the following?
```php
:
> On Thu, Sep 9, 2021 at 6:31 AM Go Kudo wrote:
>
>> Hi Nikita, sorry
2021年9月23日(木) 2:05 Dan Ackroyd :
> Go Kudo wrote:
> > Dan Ackroyd wrote:
> >> you can _simply_ include ext/random/random.h." sounds pretty
> >> dismissive of causing possibly unneeded work for downstream projects.
> >
> > The point I was trying to
2021年9月22日(水) 21:01 Aleksander Machniak :
> On 22.09.2021 13:21, Go Kudo wrote:
> > The voting phase for the following RFCs will begin as soon as two weeks
> > have passed.
>
> The RFC title is not correct English (missing "to" or "into"). The first
&g
The RFCs are in limbo, but we are currently thinking of including the
following RNGs in the proposal
- XorShift128Plus
- MT19937 (for compatibility)
- MT19937_64 (for more entropy and wider range)
While it is clear that MT19937 is simply MersenneTwister, it is not
accurate since there is MT19937_
It's been a while Internals. I'm Go Kudo.
First of all, I would like to apologize for leaving my previous RFC, object
scoped RNG, and the preliminary RFC, split random extension, without any
progress.
The implementation of these RFCs was not sophisticated and failed to be
tested for a
2022年2月14日(月) 20:40 Tim Düsterhus :
> Hi
>
> On 2/14/22 12:11, Go Kudo wrote:
> > The refreshed RFC and implementation are available at the following URL:
> >
> > https://wiki.php.net/rfc/rng_extension
> > https://github.com/php/php-src/pull/8094
> >
> &g
easy. The user
will always have to worry about the buffering size of the Randomizer.
> Why xorshift instead of xoshiro / xoroshiro?
The XorShift128Plus algorithm is still in use in major browsers and is dead
in a good way.
Also, in our local testing, SplitMix64 + XorShift128Plus performed well in
terms of performance and random number quality, so I don't think it is
necessary to choose a different algorithm.
If this RFC passes, it will be easier to add algorithms in the future. If a
new algorithm is needed, it can be implemented immediately.
Regards,
Go Kudo
2022年2月15日(火) 19:03 Tim Düsterhus :
> Hi
>
> On 2/15/22 04:58, Go Kudo wrote:
> >> Regarding "unintuitive": I disagree. I find it unintuitive that there
> are
> > some RNG sequences that I can't access when providing a seed.
> >
> > This
2022年2月15日(火) 22:09 Tim Düsterhus :
> Hi
>
> On 2/15/22 12:48, Go Kudo wrote:
> > At first, I updated the RFC to the latest status.
> >
> > https://wiki.php.net/rfc/rng_extension
>
> Thank you, the examples are useful.
>
> > I need some time to think
2022年2月16日(水) 20:24 Tim Düsterhus :
> Hi
>
> On 2/16/22 12:04, Go Kudo wrote:
> > Thanks for the good idea. I changed the NumberGenerator to Engine and
> > changed generate() to return a string as suggested.
>
> Thanks, I've already seen the updated PR and played a
2022年2月16日(水) 21:25 Tim Düsterhus :
> Hi
>
> On 2/16/22 12:39, Go Kudo wrote:
> >> Is the nextByteSize() method actually required? PHP strings already
> know
> > their own length.
> >
> > This is a convenience of the current implementation.
>
> You
2022年2月17日(木) 19:25 Tim Düsterhus :
> Hi
>
> On 2/17/22 08:37, Go Kudo wrote:
> > The following points have been fixed:
> >
> > - `nextByteSize(): int` has been removed from Random\Engine
> > - If the width of the RNG is statically defined, it will now be us
2022年2月17日(木) 19:25 Tim Düsterhus :
> Hi
>
> On 2/17/22 08:37, Go Kudo wrote:
> > The following points have been fixed:
> >
> > - `nextByteSize(): int` has been removed from Random\Engine
> > - If the width of the RNG is statically defined, it will now be us
2022年2月18日(金) 19:46 Tim Düsterhus :
> Hi
>
> On 2/18/22 07:31, Go Kudo wrote:
> > I have been looking into output buffering, but don't know the right way
> to
> > do it. The buffering works fine if all RNG generation widths are static,
> > but if they are dynami
2022年2月21日(月) 21:44 Tim Düsterhus :
> Hi
>
> On 2/21/22 03:57, Go Kudo wrote:
> > I am sorry for the delay in replying.
>
> Don't worry, there was a weekend inbetween and I totally understand that
> one wants to take their weekend off.
>
> > Thank you for
that PHP RFCs tend to become more controversial once the
voting phase begins.
Therefore, I would like to solicit feedback on this RFC, whatever it may
be. (Just only positive or negative feedback would be okay)
Regards,
Go Kudo
2022年3月10日(木) 3:57 Tim Düsterhus :
> Hi
>
> On 3/9/22 11:48, Go Kudo wrote:
> > Proposed RFCs and implementations have been reorganized. The main changes
> > are as follows
> >
> > https://wiki.php.net/rfc/rng_extension
> > https://github.com/php/php-src/
2022年3月10日(木) 3:07 Larry Garfield :
> On Wed, Mar 9, 2022, at 4:48 AM, Go Kudo wrote:
> > Hello internals.
> >
> > Proposed RFCs and implementations have been reorganized. The main changes
> > are as follows
> >
> > https://wiki.php.net/rfc/rng_extension
At present, PHP cannot be built using LTO (Link Time Optimization).
LTO is a compiler feature that can improve performance by optimizing at
link time.
Chromium is also using this feature.
https://gcc.gnu.org/onlinedocs/gccint/LTO-Overview.html
The reason for the LTO failure appears to be the Zen
compatibility issues with PHP 8.2 in test cases
- More detailed description in RFC
Previous discussion thread: https://externals.io/message/117295
Voting will begin at 2022-06-14 00:00:00 (UTC).
https://wiki.php.net/rfc/rng_extension
Regards,
Go Kudo
2022年6月4日(土) 18:03 Côme Chilliet :
> Le 31 mai 2022 11:54:18 GMT+02:00, Go Kudo a écrit :
> >Hi internals.
> >
> >Although I have explained that due to the global turmoil I will delay
> >voting on the RFC as long as possible, it is time to start voting on the
2022年6月8日(水) 0:24 Tim Düsterhus :
> Hi
>
> On 5/31/22 11:54, Go Kudo wrote:
> > - More detailed description in RFC
> >
>
> a)
>
> For the Random\Engine interface I suggest to clarify that the returned
> bytestring will be interpreted as a little endian inte
2022年6月10日(金) 19:42 Tim Düsterhus :
> Hi
>
> On 6/10/22 12:02, Go Kudo wrote:
> >> It has a single generate(): string method that generates random numbers
> > as a binary string. This string must be non-empty and attempting to
> return
> > an empty will result i
2022年6月13日(月) 16:14 Tim Düsterhus :
> Hi
>
> On 6/13/22 04:23, Go Kudo wrote:
> > I have created a PoC that allows all internal operations to be performed
> in
> > 64-bit environments to achieve the same results, although the efficiency
> of
> > execution in 32
2022年5月31日(火) 18:54 Go Kudo :
> Hi internals.
>
> Although I have explained that due to the global turmoil I will delay
> voting on the RFC as long as possible, it is time to start voting on the
> RFC in order to get the implementation to full status by the PHP 8.2
> Fea
,
Go Kudo
1 - 100 of 148 matches
Mail list logo
