> On May 23, 2024, at 1:20 PM, Tim Düsterhus wrote:
>
> Hi
>
> On 5/22/24 02:48, Aaron Piotrowski wrote:
>> Perhaps not as clean and easy as the functionality being built-in, but it
>> gets the job done.
>
> I would suggest to use the built-in functi
_dump(ExampleEnum::from('ONE'));
var_dump(ExampleEnum::from('FOUR'));
```
Perhaps not as clean and easy as the functionality being built-in, but it gets
the job done. :-D
Aaron Piotrowski
can revoke my votes.
>I know that I sound like a snitch here
A bit. But you totally have the right to complain.
Best regards
Aaron Junker
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
work
over next weeks and months on making some Proof on Concepts and then create a
more mature RFC.
With best regards
Aaron Junker
> Hi all
>
> I will now open voting on my RFC for creating a global php.net login
> system[1].
>
> Best regards
>
> Aaron Junker
>
>
> Derick Rethans wrote:
> > On 11 June 2022 08:13:15 CEST, Aaron Junker
> wrote:
> >> Hi all
> >>
> >> I will now open voting on my RFC for creating a global php.net login
> system[1].
> >
> > I think this is not a good RFC, and very pr
Hi all
I will now open voting on my RFC for creating a global php.net login system[1].
Best regards
Aaron Junker
[1]: https://wiki.php.net/rfc/global_login
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
questions:
1. What kind of majority in votes will this RFC need to get accepted?
2. Am I allowed to vote on my own RFC?
Best regards
Aaron Junker
[1] https://wiki.php.net/rfc/global_login
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
r your concerns regarding human resources, I would do everything needed to
bring such a system to existence.
Best regards
Aaron Junker
Hi all,
I would like to start the discussion on my RFC for creating a global login
system on php.net: https://wiki.php.net/rfc/global_login.
When you have feedback to a specific point of the RFC, please use the
corresponding number used in the RFC.
Best regards
Aaron Junker
--
PHP Internals
. Be sure you don't overload your RFC with too much
> scope.
>
> --
> Cheers,
> Ben
Hi Ben
Yes, this might be out of scope. You're right.
I will try not to overload my RFC, but with all the different login systems on
php.net it might get difficult to keep it small. Still I will try my best.
Best regards
Aaron Junker
Use the account to discover how the account system works for my RFC for a
global php.net login.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
php.net credentials. But I can't find any
>information on how you get such a mail address/account or what these accounts
>are used for. So could anyone give more context on that?
>
>2. Is people.php.net still used by people? For me it does seem like something
>no one uses anymore,
x27;t find any
information on how you get such a mail address/account or what these accounts
are used for. So could anyone give more context on that?
2. Is people.php.net still used by people? For me it does seem like something
no one uses anymore, but I could be wrong.
Best regards
Aa
> > I would like to request karma to create a RFC for a global php.net login
> > system. The RFC will show up different scenarios and aspects, on which you
> > will be able to vote on, so that it gets easier to get an overview what the
> > PHP developer want.
>
Hi all,
I would like to request karma to create a RFC for a global php.net login
system. The RFC will show up different scenarios and aspects, on which you will
be able to vote on, so that it gets easier to get an overview what the PHP
developer want.
Wiki username: aaron-junker
Best regards
yes I
would love to help achieving this.
Best regards
Aaron
[1] https://wiki.php.net/ideas/phplogin
[2]
https://docs.github.com/en/developers/apps/building-oauth-apps/creating-an-oauth-app
[3] https://www.dokuwiki.org/plugin:oauth
[4] https://www.dokuwiki.org/plugin:oauthgithub
--
PHP Int
many resourceful
Best regards
Aaron
[1] https://wiki.php.net/ideas/phplogin
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
Congratulations to Sergei and Pierrick for getting elected.
I wish you and Ben all the best and a great PHP 8.2 release.
Best regards
~Aaron
From: Calvin Buckley
Sent: Thursday, May 19, 2022 1:55:41 AM
To: Ben Ramsey ; PHP internals
Subject: Re: [PHP-DEV] Re
Hi all,
The week, where applications were open is over. And I also saw the available
candidates already got mentioned on the wiki page of PHP 8.2. So I'm curious
when will voting start and how long will it last?
Thanks in advance
Aaron
From: Joe Watkins
2] and the opensource.microsoft.com repository [3][4].
My GitHub handle is aaron-junker [5].
I'm very passionate about PHP and I love programming in PHP. That's why I would
feel very honored to be a release manager for PHP 8.2.
I will soon start to learn the basics of C. That's something I wa
time to spare, but definitely not too much.
2. I don't really know C. The mail says you don't necessarily have to. I could
learn it if necessary though. So how bad would it be if I couldn't program in
or understand C?
It would be nice if someone could answer them. Thanks!
Best
t you all think.
Best regards
Aaron
From: Victor Bolshov
Sent: Wednesday, March 2, 2022 10:31:05 AM
To: internals@lists.php.net
Subject: [PHP-DEV] PHP Community to support Ukraine and help to stop Russian
agression
Hello internals.
In these dark days for humanit
ways clear which side is "right" and
which is "wrong", as in Ukraine, Russia just invaded Ukraine, without any right
to do that.
And for certain conflicts only showing a flag could provocate some people.
Best regards
Aaron
Von: naitsi...@e.m
I'm not an internal, but I support this idea.
From: Lynn
Sent: Wednesday, March 2, 2022 10:36:32 AM
To: Victor Bolshov
Cc: PHP internals
Subject: Re: [PHP-DEV] PHP Community to support Ukraine and help to stop
Russian agression
On Wed, Mar 2, 2022 at 10:31 AM V
accomplish this, such as a ref
object like
https://github.com/azjezz/psl/blob/21bf0cd3d6d6055fc88541e9b24f3140bd179b2d/src/Psl/Ref.php,
but a weak-ref to $this would certainly be more convenient.
Cheers,
Aaron Piotrowski
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
mp/blob/27219ddbc0bbc3fd0db4d7380eaed6489c7291ed/lib/functions.php#L135
<https://github.com/amphp/amp/blob/27219ddbc0bbc3fd0db4d7380eaed6489c7291ed/lib/functions.php#L135>
I agree, it is a bit unpleasant and looks like a hack. I would welcome an
isAnonymous() method.
Cheers,
Aaron Piotrowski
/pull/7155
Nothing has functionally changed about the method, only the name.
Fiber::current() is another possibility, but was not chosen because it may be
conflated with Iterator::current().
Does anyone object to this rename? Shall we have a vote or is that not
necessary?
Cheers,
Aaron Piotr
On May 14, 2021, at 7:36 PM, Larry Garfield wrote:
>
> On Fri, May 14, 2021, at 7:20 PM, Aaron Piotrowski wrote:
>>
>>> On May 14, 2021, at 7:00 PM, Larry Garfield wrote:
>>>
>>> Is that actually going to come up? Given that PHP functions (at least
>
with args bound to all four
params: `fourParams(1, 2, 3, 4, ?)`.
What would error is `fourParams(1, 3, ?, ?)`, as the second ? is meaningless.
I think you've convinced me that one-for-one matching on ? is burdensome, but
the above is a happy medium perhaps?
Cheers,
Aaron Piotrowski
--
PHP
> On May 14, 2021, at 6:09 PM, Paul Crovella wrote:
>
> On Fri, May 14, 2021 at 2:49 PM Aaron Piotrowski wrote:
>>
>> Consider `function foo(int $x, int $y, int $z) {}` with a partial defined as
>> `$partial = foo(?, 42)`.
>>
>> If the partial is c
rwarded to `$z` or
should the call error as providing too few arguments? Or perhaps should the
partial declaration should error, as it should have been `foo(?, 42, ?)` or
`foo(?, 42, ...?) so the partial provided all required arguments to foo.
Cheers,
Aaron Piotrowski
--
PHP Internals - PHP R
several years ago when I started compiling PHP
myself and was confused why `php -a` broke. An error message would have saved
me some time. So yes, please, merge it.
Aaron Piotrowski
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
n object seems like the correct approach.
>
> One thing I'm not 100% clear on from the RFC, does this also deprecate
> random_int()/random_bytes()? Those are (AFAIK) unseeded, so they seem like
> they'd continue to serve their current purpose, but it's not clear fro
ially chose `noreturn` simply because I
was familiar with the name from C and didn't have a strong opinion. However, I
agree that `noreturn` is a poor choice for reuse as a bottom type, so I changed
my vote to `never`.
Cheers,
Aaron Piotrowski
> On Mar 19, 2021, at 5:47 PM, Levi Morrison
> wrote:
>
> On Fri, Mar 19, 2021 at 3:54 PM Niklas Keller <mailto:m...@kelunik.com>> wrote:
>>
>> Hey Levi,
>>
>>> On Mon, Mar 8, 2021 at 12:40 PM Aaron Piotrowski wrote:
>>>>
>
> On Mar 12, 2021, at 4:36 PM, Christoph M. Becker wrote:
>
> On 12.03.2021 at 23:04, Michael Wallner wrote:
>
>> Thank you, and everyone involved, for your effort.
>>
>> On 08/03/2021 20.40, Aaron Piotrowski wrote:
>>> Greetings everyone!
>>
PI provided by PHP for fibers, allowing it to drop the
boost dependency.
This leads me to believe my proposal would be mutually beneficial to both your
extension and the wider PHP community that could use fibers outside of your
framework or Swoole.
Cheers,
Aaron Piotrowski
--
PHP Internals - PHP
$i) {
echo $result, "\n";
$result = $fiber->resume();
}
echo "Generated ", $i, " numbers before generating zero.\n";
```
This short script works just as expected, cool! :-D
Cheers,
Aaron Piotrowski
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
> On Mar 11, 2021, at 10:41 AM, Ben Ramsey wrote:
>
>> On Mar 11, 2021, at 10:29, Aaron Piotrowski wrote:
>>
>> There is not an internal API to create fibers at this time. However, I
>> planned to collaborate with other internals developers to add this API (a
able to
PHP extensions.
Aaron Piotrowski
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
not average PHP users, we
> believe there would be little effect to the community to take this step.
>
> Cheers,
> Aaron Piotrowski
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: https://www.php.net/unsub.php
>
Hi everyone!
I’m concerned
all the tools for fantastic, clear, intuitive user space
async code. This is the one missing piece.
Aaron Piotrowski
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
l, I do
not condone sending emails to people privately off list asking them to vote in
a particular way.
For clarification to those that may have not received the email in question, I
did not send the email nor did I request that it be sent.
Thanks,
Aaron Piotrowski
--
PHP Internals - PHP Runt
ant to be a lightweight implementation to enable user
space green-threads/coroutines. I would love to see more async tools in PHP,
but that will require much more work. This is meant to be a first step toward
that eventual goal, without conflicting with or restricting future additions.
Cheers,
ibers can certainly be done if the need
arises.
- Being marked experimental: I was hoping this would be a good compromise
between allowing people to experiment with fibers and providing the ability to
make minor BC breaks if the need arose. I realize this is generally not the PHP
way, howev
> On Mar 8, 2021, at 1:40 PM, Aaron Piotrowski wrote:
>
> Greetings everyone!
>
> The vote has started on the fiber RFC: https://wiki.php.net/rfc/fibers
> <https://wiki.php.net/rfc/fibers>
>
> Voting will run through March 22nd.
>
> Cheers,
> Aaron Pi
Greetings everyone!
The vote has started on the fiber RFC: https://wiki.php.net/rfc/fibers
<https://wiki.php.net/rfc/fibers>
Voting will run through March 22nd.
Cheers,
Aaron Piotrowski
voting on the RFC next week Monday.
If you have any questions or concerns, please do raise them now, as it’s always
more difficult to address these once voting has started.
I feel this feature deserves a lot of time to merge and test if it is to be
included in 8.1, so I’d like to move forward
> On Feb 3, 2021, at 11:32 AM, Aaron Piotrowski wrote:
>
>
>> On Jan 31, 2021, at 11:29 AM, Levi Morrison via internals
>> wrote:
>>
>> I think it would probably be advantageous to have an observer that
>> alerts interested parties when the fiber swit
> On Feb 12, 2021, at 4:05 PM, Aaron Piotrowski wrote:
>
> The Fiber API would conflict or prevent async / await from being added to PHP
> in the future. The two APIs can coexist and serve different purposes.
>
While probably obvious from the rest of the context of the ema
> On Feb 12, 2021, at 3:47 PM, Mark Randall wrote:
>
> On 12/02/2021 21:40, Aaron Piotrowski wrote:
>> I would like to open voting for this RFC around the beginning of March, so
>> please review the minimal API and provide any feedback soon.
>
> Removing the sched
> On Dec 17, 2020, at 10:30 AM, Aaron Piotrowski wrote:
>
> Hello everyone!
>
> I would like to introduce an RFC for adding full-stack fibers to PHP:
> https://wiki.php.net/rfc/fibers
>
> Fibers are primarily used to implement green-threads or coroutines for
> a
d.
Since FiberScheduler internally is just another fiber, there’s nothing really
special done to switch to a fiber scheduler. Requiring suspending to a
scheduler rather than an arbitrary fiber prevents users from attempting to
switch to an already running fiber.
Cheers,
Aaron Piotrowski
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
vi,
Yes, I agree and will look at implementing an observer API.
Cheers,
Aaron Piotrowski
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: https://www.php.net/unsub.php
> <https://www.php.net/unsub.php>
> On Jan 18, 2021, at 8:59 AM, Benjamin Eberlei wrote:
>
> Hi Aaron,
>
> this is a very interesting and welcome piece of functionality. I have gone
> through the RFC a few times now, it have never thought about or worked with
> fibers before, additional feedback will
om/amphp/amp/tree/v3/examples/pipeline or in react-fiber
https://github.com/trowski/react-fiber/tree/master/examples where the Fiber API
is handled by the library rather than “application” code.
Cheers,
Aaron Piotrowski
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
't hesitate to ask.
Cheers!
Aaron Piotrowski
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
> On Dec 21, 2020, at 4:33 PM, Mike Schinkel wrote:
>
>> On Dec 17, 2020, at 11:30 AM, Aaron Piotrowski wrote:
>>
>> Hello everyone!
>>
>> I would like to introduce an RFC for adding full-stack fibers to PHP:
>> https://wiki.php.net/rfc/fibers
>
> On Dec 17, 2020, at 4:11 PM, Saif Eddin Gmati wrote:
>
> Hello Aaron,
>
> First, I want to say that I love this proposal and would love to see it land
> in the next PHP release, but I have one question regarding this:
>
>
>> Promises result in the “What colo
Hi Peter,
> On Dec 17, 2020, at 1:23 PM, Peter Stalman wrote:
>
> Hi Aaron, this is very interesting to me. Can I ask why this approach as
> opposed to other paradigms like promises, coroutines, etc? You mentioned
> async/await in the future scope, and I assume most of these
complex feature. The RFC contains many examples and links to code
using fibers to help explain and demonstrate what is possible, however I’m
certain many more questions and concerns will arise. Looking forward to
feedback and discussion.
Aaron Piotrowski
--
PHP Internals - PHP Runtime Development
d classes probably should be used in the future, but for
logically grouped classes (such as DOM), extensions, etc.
Attributes are a basic language feature, and therefore should live in the
global namespace the same way as Throwable, Iterator, Countable, etc.
I did not want naming to be a blocker on the
ub.com/php/php-src/blob/db233501ff9d56765ef4a870b777a643c2136711/Zend/zend_exceptions.c#L909-L916
>>
>> <https://github.com/php/php-src/blob/db233501ff9d56765ef4a870b777a643c2136711/Zend/zend_exceptions.c#L909-L916>
>>>
>>> No catch block would catch it, because it wouldn't implement Throwable
>> nor extend Exception or Error.
>>>
>>
>> Very elegant solution!
>>
>> PS: Naming things is hard, but `Throwable` could not have been a
>> better choice in retrospect. Ty ;)
Thanks! Every once-in-a-while I manage to name something correctly!
>>
>>> Aaron Piotrowski
>>>
>>
>> Márcio
Aaron Piotrowski
ace, which is rather odd. It still allows
> explicitly catching the exit.
>
> 3. Introducing a function like catch_exit(function() { ... }). This would
> still allow catching exits (for phpunit + daemon use cases), but the fact
> that this is actually implemented based on an exception would be hidden and
> the only way to catch the exit is through this function.
>
> 4. Don't allow catching exits at all. In this case the exception is just an
> implementation detail.
>
> Nikita
+1 for option 3.
EngineShutdown could be a special exception to the engine, being handled like
an exception internally, but not implement Throwable and therefore not an
exception from user-land's point-of-view.
EngineShutdown could be added to the list of "throwables", but forbid
instigation in user-land.
https://github.com/php/php-src/blob/db233501ff9d56765ef4a870b777a643c2136711/Zend/zend_exceptions.c#L909-L916
No catch block would catch it, because it wouldn't implement Throwable nor
extend Exception or Error.
Aaron Piotrowski
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
act.
> What keywords do you like for fibers and why do we need them?
> Why do we need Promise/Awaitable in the core?
> If you have concrete solution (just API), lets discuss it in separate email
> thread.
Niklas and/or I will put something together and start a new thread.
Regards,
Aaron Piotrowski
er unexpected
behaviors. I think PHP is absolutely ready to shine in environments outside of
per-request SAPIs. Core support for async is one of the few ingredients missing.
Aaron Piotrowski
[1] https://github.com/amphp/green-thread
[2] https://github.com/am
ed from methods, named functions, etc with less boilerplate.
Thanks to you and Dmitry for working on this!
Aaron Piotrowski
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
oloading and further optimizations.
+1
Aaron Piotrowski
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
;ed on a constructive comment, or
too little is filtered and there's still noise from those replying to the
filtered user. Banning or suspension should not be used lightly, but I think
we've reached a point where it is warranted.
I think a simple PHP CoC similar to the JS Foundation [1]
> On Jun 7, 2017, at 6:31 AM, Derick Rethans wrote:
>
> I voted no because of the BC break.
>
Changed my vote to no for the same reason. The subtly of the BC would make bugs
potentially difficult to discern. Would happily vote yes again for an RFC
targeting 8.
Aaron Piotr
confusing when something like `|| => $x ** 2` may be
more confusing, so point taken. Regardless, I still prefer the visual
difference since the auto-capture behavior is so different from other functions.
Cheers!
Aaron Piotrowski
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
> On Feb 3, 2017, at 9:06 PM, Stephen Reay wrote:
>
>
>> On 4 Feb 2017, at 07:25, Aaron Piotrowski wrote:
>>
>> $callback = |int|float $x| => $x ** 2;
>
> Forget the parser, you're giving my eyes diabetes trying to read that.
I absolutely agree th
nd | is not followed by =>, the parser should be able to discern
that a union type is being used.
Regards, Aaron Piotrowski
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Below are a couple of real-world single line closures using the proposed syntax:
[1] Loop::defer(|| => ($this->when)($exception, $value));
[2] $this->watcher = Loop::delay($time, || => $this->resolve($value));
IMHO, the reduced boilerplate required makes it easier to discern what
als for legacy app support purposes.
>
>
> On 16 Nov 2016 11:50, "Aaron Lewis" wrote:
>>
>> I have a file that contains a HTTP request,
>>
>> ```
>> GET /xxx.php
>> Host: xxx
>> Content-Type: xxx
>> ...
>> ```
>>
>&
s though, I'd look there for inspiration ... there's also
> an HTTP parser included in there ...
>
> Cheers
> Joe
>
> On Wed, Nov 16, 2016 at 10:50 AM, Aaron Lewis
> wrote:
>>
>> I have a file that contains a HTTP request,
>>
>> ```
>> G
API myself.
So far I've found sapi_post_entry, but I couldn't get the whole
picture. Where's the entry point of request parsing?
--
Best Regards,
Aaron Lewis - PGP: 0x13714D33 - http://pgp.mit.edu/
Finger Print: 9F67 391B B770 8FF6 99DC D92D 87F6 2602 1371 4D33
--
PH
Hi Marco,
> On Aug 19, 2016, at 1:31 PM, Marco Pivetta wrote:
>
> Hi Aaron et all,
>
> I tried to implement support for 7.1 in zend-code as a start:
>
> https://github.com/zendframework/zend-code/pull/87
>
> A few issues arise:
>
> * `ReflectionType#__toStri
k of, and it would break existing code.
It sounds like you'd prefer the ? was not prepended to the string as well, is
that correct? Again it sounds like it would be better to use methods other than
__toString(). I understand __toString() was the only way to get the type name
before, but n
llable types just created
another headache for you. :-(
Aaron Piotrowski
[1] https://github.com/php/php-src/pull/2068#issuecomment-239983716
(Forgot to CC internals again... ugh)
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
pe::__toString() will return
"?\Type\Name" or without the changes I committed it would return "?Type\Name".
If you need the type name without the leading ? or \, use
ReflectionNamedType::getName().
It would be nice to have no BC breaks, but right now I'm not seeing a
.
If anyone has objections to these changes, please let me know.
Thanks!
Aaron Piotrowski
[1]
http://git.php.net/?p=php-src.git;a=commitdiff;h=20fdd47921f423728b409fd0ae0106dab9c34573
[2] http://news.php.net/php.internals/94452
[3] https://wiki.php.net/rfc/reflectiontypeimprovements
[4] https
Hi Levi,
> On Jul 9, 2016, at 10:12 AM, Levi Morrison wrote:
>
> On Sat, Jul 9, 2016 at 8:16 AM, Aaron Piotrowski <mailto:aa...@trowski.com>> wrote:
>>
>>
>> Additionally, I propose adding a getName() method to ReflectionType that
>> return
ility. Casting should
not be required to get information from an object, but currently this is the
only way to get the type name from ReflectionType. Most other reflection
classes include a getName() method, this seems to have been an oversight.
Joe and Davey, what are your thoughts on this?
at it will still work, but stdClass would not
> be instanceof Iterable?
That code will continue to work just as it always has. stdClass will not be
accepted by the iterable type.
Aaron Piotrowski
was a reasonable and simple requirement to allow an
instance of stdClass to be iterable. I do not think stdClass was designed for
iteration, but rather is just used this way because of the behavior of foreach.
I'd prefer json_decode() to return an iterable object... maybe an RFC for
another day.
Aaron Piotrowski
Hi Chris,
> On Jun 30, 2016, at 6:15 AM, Christopher Jones
> wrote:
>
> Hi Aaron,
>
> I was someone who spent time on the RFC template to try and get better
> quality and to capture more information about each RFC. I think your
> RFC needs a lot more content
ting actually opens. There seems to be a pattern
of issues with RFCs not being discussed until voting has begun. The pre-vote
phase could replace one week of the discussion period, so an RFC would still
only need a minimum of two weeks between announcement and voting.
Cheers!
Aaron Piotrowski
--
to modify overall
error handling in each extension. I would rather individual extension
maintainers make decisions on error levels.
Thanks!
Aaron Piotrowski
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
om/php/php-src/pull/1942
<https://github.com/php/php-src/pull/1942>
Aaron Piotrowski
Hello,
Voting on the Iterable RFC has opened and will remain open until 7/2/16 at
11:59 GMT.
https://wiki.php.net/rfc/iterable
Thanks!
Aaron Piotrowski
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
> On Jun 18, 2016, at 6:11 PM, Dan Ackroyd wrote:
>
> Hi Aaron,
>
>> does anyone have any further feedback on this proposal?
>
> What is the performance impact of the RFC on the standard performance
> benchmarks?
>
> And can you comment on the performanc
Hi all,
I plan on bringing the iterable RFC (https://wiki.php.net/rfc/iterable) to a
vote in about a week, does anyone have any further feedback on this proposal?
Thanks!
Aaron Piotrowski
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net
/throw_error_in_extensions
PR: https://github.com/php/php-src/pull/1942
Thanks!
Aaron Piotrowski
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
/rfc/iterable
<https://wiki.php.net/rfc/iterable>
Thanks!
Aaron Piotrowski
> On Jun 1, 2016, at 3:56 PM, Rowan Collins wrote:
>
> On 01/06/2016 19:36, Aaron Piotrowski wrote:
>> While this might be considered a BC break, I can't imagine there's an actual
>> code out there relying on suppressing the warning just to call a function
>
ious reason. A function should not be called if too few
arguments are provided.
While this might be considered a BC break, I can't imagine there's an actual
code out there relying on suppressing the warning just to call a function
without enough arguments. I see no problem putting
is is somewhat off-topic of this particular RFC, since we can already
do general type-aliasing with `use`,
use SomeFoo as Foo;
perhaps similar syntax could be used for type expressions, eliminating the need
for a new keyword.
use callable(int, int): int as IntReducer;
use array | Traversable as Itera
e functions. Setting a custom error handler before calling these
functions and removing the error handler afterwards is a clunky solution. Any
proposal to remove the @ operator needs to address how functions issuing
unavoidable warnings will be changed.
Aaron Piotrowski
https://trowski.com
@trowski2002
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
eption($message);
}
There is no way of knowing if the stream buffer is full before calling
fwrite(), resulting in a warning and 0 being returned. IMO, just 0 should be
returned without issuing a warning.
Aaron Piotrowski
https://trowski.com
@trowski2002
--
PHP Internals - PHP Runtime Devel
1 - 100 of 173 matches
Mail list logo
