Nick Hill fb0d34a2f9 Avoid synthetic methods in Recycler (#9736) ... Motivation Currently the visibility of the various Recycler inner classes and their fields isn't optimal. Some private members are accessed by other classes resulting in synthetic methods, and other non-private classes/members are only accessed privately and so can be made private. Modifications - Increase/reduce visibility of various fields/methods/classes within Recycler - Have WeakOrderQueue extend WeakReference<Thread> to eliminate the owner field - Change local DefaultHandle var to DefaultHandle<?> to avoid raw type compiler warning Result Tidier code, fewer implicit methods on hot paths (reducing inlining depths)		2019-10-31 11:22:05 +01:00
..
src	Avoid synthetic methods in Recycler (#9736)	2019-10-31 11:22:05 +01:00
pom.xml	Add BlockHound integration that detects blocking calls in event loops (#9687)	2019-10-25 06:14:14 -07:00