Skip to content

Conversation

@serprex
Copy link
Contributor

@serprex serprex commented Feb 19, 2025

addresses #423 however as of 1.23 the issue is moot & this was never really leaking since the 1 second would generally pass

this does slightly reduce allocations, but this is on an error path, so not valuably

Implemented as proof of concept, #423 can be closed

@dveeden
Copy link
Collaborator

dveeden commented Feb 19, 2025

Thanks. Interesting. If I understand things correctly this is mostly a FYI and should be closed?

@serprex
Copy link
Contributor Author

serprex commented Feb 19, 2025

@dveeden yes

@serprex serprex closed this Feb 19, 2025
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