* don't enforce async calls for thread-safe listeners (closes#1551)
* cleanups, remove structure compiling
* improve cloning a bit
* fix small issue in no-op structure modifier
* remove last usages of FieldUtils
* improve and fix equality check in container test
* Replace guava Charsets with StandardCharsets.
* Use try-with-resources
* Faster Util asList, inline getOnlinePlayers.
* Use direct ArrayList allocation.
* Use new instead of Lists#...
* Use new instead of Lists#...
* Faster looping.
* Use switch.
* Remove diamond operators.
* Use ArrayDeque instead of LinkedList.
* Actually conform to the documentation and always use an ArrayList as backing list.
* Potentially breaking change: Use switch instead of startsWith as this e.g. causes "n" to be interpreted as "names" and any future new commands starting with "n" will be ignored.
* Use addAll().
* Remove IntegerSet. Unused and also covered by fastutils IntSet.
* Much faster boolean parsing. Might have breaking changes as parameterName is now checked after the false block.
* Make most fields final, fix JavaDoc and remove diamond operators.
* Make fields final.
* Much cleaner getAllInterfaces() method.
Co-authored-by: Dan Mulloy <dev@dmulloy2.net>
- The gclib dependency in the EnchancerFactory has been removed. All classes that used the actual factory part of it have been updated to use bytebuddy instead. This class will have to be removed at some point, but at the moment it is still used for accessing its class loader.
- Renamed EnhancerFactory to ByteBuddyFactory. All ByteBuddy actions should go through this now. Every subclass created here implements the ByteBuddyGenerated interface. This makes it possible to recognize classes generated using ByteBuddy (by default, it doesn't leave such a trace).
- Removed the method DefaultInstances#forEnhancer(Enhancer). This method isn't used anywhere; the last trace of usage of the method I could find was in 2013 (in the NetworkServerInjector). External plugins (I couldn't find any that used it), they should really have their own implementation, given that they already require an instance of an Enchancer. As such, I feel it is safe to remove rather than update it.
