Seems like a good change

I don't see why this would be a good change. Accessors just adds more interface classes to the project for no benefit. Accessor mixins are also slightly worse performing during runtime than access wideners.

I don't see why this would be a good change. Accessors just adds more interface classes to the project for no benefit. Accessor mixins are also slightly worse performing during runtime than access wideners.

@RaphiMC Hey, please read this, it gives some information about why accessor mixins would be better, in cases such as safety.

I don't see why this would be a good change. Accessors just adds more interface classes to the project for no benefit. Accessor mixins are also slightly worse performing during runtime than access wideners.

@RaphiMC Hey, please read this, it gives some information about why accessor mixins would be better, in cases such as safety.

I glanced over it and couldn't find any good/applicable reasons why I should switch to mixin accessors.

I doubt accessor mixins are less performant to be honest, but I personally see no reason to switch.

I doubt accessor mixins are less performant to be honest, but I personally see no reason to switch.

The JVM most likely optimizes the casts and method invocations, but it still makes the code look uglier for no benefit