I think the EXPRENT_FIELD condition exists in case the field's initializer depends on a prior field in the same class. We already handle this case in the deobfuscator, which ensures fields appear in exactly the order in which they are first written to in the <init> and <clinit> methods. (This isn't perfect, as we ignore the problem of multiple <init> methods writing fields in different orders to each other, but it seems good enough for the client.)master
parent
1526cea2a5
commit
b3a455fb1a
Loading…
Reference in new issue