Skip to content

Conversation

strpbrk
Copy link

@strpbrk strpbrk commented Dec 4, 2021

I have managed to implement it with minimal impact on dependencies, and should work correctly up to the latest dependencies.

@HighCommander4
Copy link
Contributor

@strpbrk just to confirm my understanding, this patch has the issues described in this comment, and is thus not suitable to be reviewed and merged in its current form, right?

@strpbrk
Copy link
Author

strpbrk commented Jul 29, 2025

@HighCommander4 it has at least those issues. More issues may have been introduced with API changes over the years, which I have not tracked. If I ever make time to get back to this problem, I will make a new evaluation, bug reports, pulls, etc.

@HighCommander4 HighCommander4 marked this pull request as draft July 29, 2025 21:03
@HighCommander4
Copy link
Contributor

@HighCommander4 it has at least those issues. More issues may have been introduced with API changes over the years, which I have not tracked. If I ever make time to get back to this problem, I will make a new evaluation, bug reports, pulls, etc.

Thanks. I've marked this PR as a "draft" to make it clear that it's not ready for review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants