Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Deprecate LockFreePool implementation from 2.18, remove from 3.0? #1271

Open
cowtowncoder opened this issue Apr 20, 2024 · 2 comments
Open

Deprecate LockFreePool implementation from 2.18, remove from 3.0? #1271

cowtowncoder opened this issue Apr 20, 2024 · 2 comments
Labels
2.18 Issues planned at earliest for 2.18

Comments

@cowtowncoder
Copy link
Member

Due to reported issues wrt Lock-Free pool implementation (temporarily used as the default RecyclerPool for 2.17.0), its use seems dangerous. If we cannot solve (or at least severely mitigate) the problems, it seems necessary to deprecate this implementation, and remove from 3.0.

No decision is yet made but I created this issue so we can consider it.
@cowtowncoder cowtowncoder added the 2.18 Issues planned at earliest for 2.18 label Apr 20, 2024
@cowtowncoder
Copy link
Member Author

/cc @mariofusco @pjfanning @JooHyukKim @franz1981

@JooHyukKim
Copy link
Member

JooHyukKim commented Apr 20, 2024 •
edited

(Just connecting things) Issue stemmed out from #1260 (comment).

The issue can also start with "Fix or deprecate" to align with the original comment.

@cowtowncoder cowtowncoder mentioned this issue May 5, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
2.18 Issues planned at earliest for 2.18
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@cowtowncoder @JooHyukKim