[Request] @ExpectPlatform fields

[KP2048]

Say I have an abstract class in common module that extends from Block class. But I need to have some different code in fabric vs forge. I would implement that abstract class in both forge and fabric modules. This is fine, but now I have 2 RegistrySuppliers and neither are accessible from common module. What I have been doing to work around this is making a public static but not final RegistrySupplier field in common module, but not assigning a value to it and in forge and fabric modules under a static {} block setting the common field to a registered value.
this works, but it would be much more neat and convenient if I could use something like expectplatform to make sure the field has the correct value. This would also make final fields possible in this situation

[Juuxel]

This can already be done by making the code in your field initialiser into an @ExpectPlatform method without needing @ExpectPlatform fields.

[KP2048]

But then I’d have to make a separate method for each field…

[shedaniel]

How would expect platform fields even work?

[KP2048]

Autogenerated Methods with reflection?

[wagyourtail]

in <clinit> to access the impl's field's value