Re: [RFC]I'd like to see the RFCs that deprecate the FFI non-static approach start voting
| From: | Saki Takamachi | Date: | Sat, 06 Jul 2024 09:55:02 +0000 |
| Subject: | Re: [RFC]I'd like to see the RFCs that deprecate the FFI non-static approach start voting | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-124244@lists.php.net to get a copy of this message | ||
Hi,
>> The reason I'm not so polite is because I'm so angry. Firstly, the Deprecate
>> functions with overloaded signatures RFC's approach to FFI recommendations is unfounded, and
>> secondly, the PR
>> commit(https://github.com/php/php-src/commit/4acf0084dcd63ec369a610ec966db33f322694c8) has not been
>> voted on by the RFC, and the implementation is very simple and crude, and does not solve the problem
>> that FFI's API is not so elegant (At the very least, there are shortcomings such as
>> complicated API calls, mixed use of multiple types of functions, and reduced performance).
>> There are so many masters,I don't understand why it was merged. The commit
>> implementation was not voted on, and it is possible to withdraw it first.
>
> If I'm not misunderstanding something, they were voted on.
>
>
> https://wiki.php.net/rfc/deprecate_functions_with_overloaded_signatures
>
> Regards,
>
> Saki
I may have misunderstood what you were saying.
I'm starting to get a little confused.
What exactly do you mean by voting on a commit?
Regards,
Saki