Interface methods overriden by a superclass method are not remapped properly

[BoogieMonster1O1]

This is a bit hard to explain, but i'll try my best A and B are two classes where B has method a which is final. C is an interface which also has a method a. C is implemented by A

public class B {
  public final void a () {}
}

public class A extends B implements C {
}

public interface C  {
  void a ();
}

Calling A.a isn't suppposed to throw an AbstractMethodError as the final superclass method overrides it. However, C.a and B.a aren't remapped properly, causing an AbstractMethodError to be thrown when calling A.a in production. C.a and B.a should get the same intermediary name. This isn't the case though

This directly relates to https://github.com/Legacy-Fabric/fabric-loader-1.8.9/issues/1

[i509VCB]

Is there any reflection occurring in this case?

Otherwise I'd either say it's mappings or tiny-remapper.

[modmuss50]

Does this ever happen in official fabric? It would be useful to have something that happens in official fabric.

[modmuss50]

Failing that a simple way to repoduce the issue would be helpful.

[BoogieMonster1O1]

https://imgur.com/qvkAc7I can confirm that it happens on official fabric (the title screen version doesnt have Fabric in it when using official fabric loader)

[hYdos]

https://imgur.com/qvkAc7I can confirm that it happens on official fabric (the title screen version doesnt have Fabric in it when using official fabric loader)

i think they meant with their intermediaries.