-
Notifications
You must be signed in to change notification settings - Fork 564
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
Reason why the MpscLinkedAtomicQueue class is final? #208
Comments
Thanks for reporting! |
FYI: This regressed after the fix and made it back into 2.1.2, still can't extend. |
franz1981
added a commit
to franz1981/JCTools
that referenced
this issue
Mar 1, 2019
kay
added a commit
that referenced
this issue
Mar 3, 2019
Fixes #208: MpscLinkedAtomicQueue can be made not final
kay
added a commit
to kay/JCTools
that referenced
this issue
Mar 3, 2019
Reported in JCTools#208, fixed but subsequent regressed as fix edited generated source. This change should fix it permanently.
kay
added a commit
to kay/JCTools
that referenced
this issue
Mar 3, 2019
Reported in JCTools#208, fixed but subsequent regressed as fix edited generated source. This change should fix it permanently.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm implementing time sliced self processing queues, and this is the only instance of the backing queue for which I need to wrap instead of extending the class. I'm fine with methods being final, but I cannot understand why the class itself cannot be extended in this specific case?
The text was updated successfully, but these errors were encountered: