Mumfrey

It depends on when you need to detect the presence of the mixin, before the classload or after. If it's after classload you can use [`Mixins::getMixinsForClass`](https://github.com/SpongePowered/Mixin/blob/master/src/main/java/org/spongepowered/asm/mixin/Mixins.java#L171), if before then it...

Yeah the entire point of `@Unique` is "I am adding this and don't intend to accidentall clobber an existing member, so needing it to match doesn't make sense, it's just...

Whilst I don't have a problem with the functionality in principle, I know next to nothing about Kotlin besides what Kyle has mentioned to me over the last couple of...

> This is what I would recommend in general with using Mixins with Kotlin for the time being, until it's "officially supported". Simply treat the Mixin file as a header...

The more I think about it the more this makes sense as at least a pale reflection of what I always really wanted *rerouters* to do. `@Redirect` is already fairly...

> To conclude, mixin is way too aggressive in its checks globally which impedes its capacities. It's not "too aggressive", this is by design, so it's exactly as aggressive as...

Thanks for the detailed write up. I now understand why I was getting spurious reports of calls to undefined static accessor methods pertaining to fabric's fork. I will look into...

This is already roadmapped for version 0.10. It's not so much localcapture as you know it from `CallbackInjector`, but a more expressive syntax for injectors in general. A lot of...

Yeah this is not a new problem, I think the specific issue is with `final` here, since the visibility issue has been trodden and re-trodden. The main discussion for overwrites...

> Ideally superinterfaces that are Mixins would have the same handling as superclasses that are Mixins, but an acceptable alternative would be providing a more clear & specific error message...