Validate shadow methods/fields and injections at compile time about mixin HOT 3 CLOSED

Warning is definitely possible. It could never fail a build because there are perfectly valid circumstances in which a shadow field or method may not exist at compile time, or may not be visible via Mirror.

It's worth bearing in mind that the information the AP has to work with is kind of limited. Mirror is pretty shite and also can't account for things which are added at runtime (such as fields added to a target class by another mixin) and doesn't provide access to anything synthetic and/or inner. I could in the future simulate some of this up to a point, but recreating the entire mixin architecture inside the AP isn't really feasible.

I can try to add what output I can, but failing a build with these checks would be absolutely unworkable so it would rely on people actually reading the build output, and I'm not sure this has much in the way of advantages over developers just getting into the habit of running an audit before committing changes.

from mixin.

@Mumfrey Speaking of running an audit, is there a way to force-load all the classes (to check for apply errors) but without generating all the implementation reports? This is spamming the console quite a lot, but it is not running the audit if CHECK_IMPLEMENTS is not set.

from mixin.

I could probably remove the CHECK_IMPLEMENTS requirement on the audit pass.

from mixin.