-
-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deleting the issue of breaking changes with no explanations? #107
Comments
I've closed your previous issue as I felt is had been answered, I haven't deleted anything. I really don't like your tone here, so I'm closing this one as well. |
This does not change things much. You just distance yourself from the answer as I'm now left in the unknown as to what to do. |
Also you should not be a maintainer of this lib if my questions is out of your scope. |
You're using an open source project. You haven't bought a product with a support contract. I don't have the time to do the research for you. If you want to use an unreleased version, you'll need to do it yourself or pay someone to do it for you. In fact, the same is true for any released version. We usually provide changelogs, but there's neither a guarantee for that nor a guarantee that the changelog is complete. |
**In reference to:** amphp#106, amphp#107, amphp#94, amphp#98, amphp#93, amphp#92, amphp#86, amphp#84, amphp#82, amphp#64 - BC signature changes has been revert since some of the tests wasn't changed to match, and too far off original design. - Using current **Libuv** version or systems installed one, not `pecl`, this setup is not reliant on the really slow `pecl` system for updated installations. The whole `uv_queue_work()` will need to be re implemented, the core internal `TSRM.c` thread related `tsrm_***_interpreter_context` functions used in PHP 7.4 has been removed since PHP 8.0.
Wow, wow, wow. Really?
Why are you wasting your time with this lib?
P.S.: This is my last question, no worries, won't bother you no more. Narcissistic people.
The text was updated successfully, but these errors were encountered: